Separate InstaScale out from default KFDEF

[anishasthana]

Most users will always want MCAD available in their clusters, but they may not want InstaScale. We should separate out InstaScale into a separate overlay/manifest set so as to increase the flexibility of deployment.

[jbusche]

I wonder if it might be possible to add to the CR the image for these KFDEF? For example, instead of using

quay.io/project-codeflare/instascale-controller:latest

I wonder if it'd be possible to override the image, cpu, memory so they could be changed just by editing the CR?
Like being able to override to this:

quay.io/project-codeflare/instascale-controller:v0.0.2

[jbusche]

Would it have it's own kfdef maybe? Then when we're doing the E2E tests, we could check the existence of the instascale kfdef and make sure it's deleted/resources are gone.

[anishasthana]

1. Yeah, we could definitely add those to the CR.
2. re: the kfdef thing, yeah, that's an option!

[accorvin]

We've discussed putting the image in the CR in recent team meetings and explicitly said we don't want to do this. The thought was that a specific version of the codeflare operator should be tied to specific versions of the operands, enduring deterministic behavior for a given version of the stack.

[astefanutti]

Closing as it's become obsolete with the operator redesign.