-
Epic
-
Resolution: Unresolved
-
Blocker
-
None
-
None
-
None
-
openstack-operator bundle respin
-
32
-
False
-
-
False
-
OSPRH-11298Reduce the RHOSO operator bundle sizes
-
Not Selected
-
Committed
-
Proposed
-
To Do
-
OSPRH-11298 - Reduce the RHOSO operator bundle sizes
-
Proposed
-
Proposed
-
100% To Do, 0% In Progress, 0% Done
-
-
-
Critical
The OpenStackControlplane CRD is quite large. That in addition to other Dataplane CRDs leaves us fairly close the the bundle size limit for OLM. In order to make space for an inevitable V2 of the OpenStackControlplane CRD we need to reimagine how to install our CRDs.
A proposed solution is to create CRDs ourselves in our own reconciler and then store them in a container we control. By doing this we avoid bundle size issues altogether.
We would do this by creating a 'meta' resource which the administrator would create once per OCP cluster to provision and install the operators, install CRDS, setup RBAC, etc. for all our operators.
Our product will still "use" OLM and get deployed by the OLM catalog but only the openstack-operator will have a true bundle. This bundle would contain a single CRD for 'OpenStack' (or OpenStackCluster perhaps) that would upon creation and reconcile install all the rest of the operators.
We will use renovate jobs to "promote" new CRDs, rbac, deployments for the service operators. Once promoted the openstack-operator will be able to deploy things directly.
- is depended on by
-
OSPRH-11123 Set more strict version dependencies between openstack-operator and services operators
- New
- links to