[Feature] Multiple Operators and CRD management

[SimonBaeumer]

Problem For the ACS cloud service we run ACS Central instances bin-packed and want to deploy different versions. Our operator has a 1:1 version mapping which requires running the operator in different versions in the same cluster. Challenging is ensuring CRD compatibility between all operators. Our CRDs are backward-compatible, thus we can install the latest CRD version. In saas deployments we do not follow SemVer, instead we use commit refs and timestamps to identify a release which makes it impossible for us to compute a version to install the CRD.

Solution An option on the operator resources which indicates OLM whether it should install the CRD would solve this issue for us.