wmhutchison
commented
1 week ago Reviewed operators which we now manage version for which are technically out of date within CCM. The following for now are just my musings, but if other team members approve, might go towards documentation efforts for classifying out we handle the various operators we now version-manage in CCM.
Operators which are a component in the creation of apps (RH Integration, JBoss EAP) are out of scope, those need separate consideration/handling. Operators which are a fairly used feature (GitOps, Pipelines) by the community ideally should be left to be handled when an OCP upgrade event awaits or someone asks for this for a valid reason. Also out of scope. Web Terminal operators would be normally in scope, but only if a suitable PR is created/merged/tested in LAB prior to Friday. Thus out of scope for this round, but will consider the next time I handle CCM (PR created/approved/merged by the Wednesday prior to allow some LAB bake-in). ACS should also be considered for upgrades more often, but like Web Terminal, needs to be planned so that LAB ACS has some bake-in time. Will look to see if LAB/PROD clusters have version separation in case we need LAB bake-in to take multiple CCM release cycles. Out of scope for now.
For next week, am not upgrading any of the mentioned operators in LAB or PROD.
One to-do is to see how well these operators show up in Red Hat's errata link, as we might consider out of band operator upgrades if there's a decent reason behind it (adverse bugfix, or security concerns). Will see if this can be automated with consistency or not.
Describe the issue This ticket will track efforts spent toward creating the next CCM release and promoting it against the three production Openshift clusters.
Definition of done