Value Statement

OLM introduced a new CustomResourceDefinition called the OperatorCondition allowing operators to communicate conditions to OLM. The Upgradeable “OLM Supported Condition” prevents the existing CSV from being replaced by a newer version of the CSV. When the Upgradeable condition is set to False, OLM will prevent a channel entry in a subscribed package that replaces the operator’s existing CSV from leaving the PendingPhase.

We should leverage the OperatorCondition to prevent OLM from upgrading to a new operator version before the operand (MCE/MCH) has caught up to the desired version.

Definition of Done for Engineering Story Owner (Checklist)

• Operator prevents OLM upgrade while operand upgrade is in progress
• Operator sets default conditions before the pod’s ready probe is set to true
• Once operand upgrade is complete, hold is released so OLM can upgrade operator again
• Operator checks that currentVersion == operator version before giving green light for upgrade

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.