Background:

• Conceptually, OLM has historically considered all operators in a namespace at a single time rather than upgrading operators individually. This has prevented us from hitting nasty version deadlock edge-cases, as described here.
• Unfortunately, customers frequently hit cases where one operator is unable to upgrade, thereby preventing any operator in the namespace from upgrading.
• We should consider how each approach may affect circular dependencies: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/dependency-resolution.md#example-version-deadlock
  • There are currently a few operators that introduce circular dependencies, one of which is ODF, MCG, OCS.

Goals:

• The goal of this ticket is to consider our past approaches and how they can best be applied to our new operator singleton design.

Acceptance Criteria:

• We have documented whether or not Operator CRs are reconciled in parallel or serially.

Upstream Issue:

• https://github.com/operator-framework/deppy/issues/75