:sparkles: Propagate ClusterExtensionRevision conditions to ClusterExtension status by perdasilva · Pull Request #2281 · operator-framework/operator-controller

perdasilva

perdasilva

perdasilva

perdasilva

pedjak

pedjak

pedjak

pedjak

Copilot AI review requested due to automatic review settings

November 5, 2025 17:42

Copilot AI review requested due to automatic review settings

November 10, 2025 17:08

perdasilva

perdasilva

perdasilva

perdasilva

perdasilva

Copilot AI review requested due to automatic review settings

December 9, 2025 12:11

@openshift-ci openshift-ci bot added the approved

Indicates a PR has been approved by an approver from all required OWNERS files.

label

Dec 10, 2025

Copilot AI review requested due to automatic review settings

December 10, 2025 11:37

@pedjak

… status

* `ClusterExtension`'s `Available` and `Progressing` conditions are equal to the counterparts on the latest installed active revision
* When a new revision is rolling out, mirror its `Progressing` condition to its counterpart on `ClusterExtension` to improve visibility
  and to signal that a transition is in progress
* Adds `.status.activeRevisions` field to the `ClusterExtension` to track the active revisions and mirrors `Available` and `Progressing` conditions for those
  not marked yet as installed

This changes opens up a possibility for an observer to get insights on `ClusterExtension` update process:
* When Reason on `Progressing` condition flips to `RollingOut`, an update is in progress
* More then one revision could be listed under `.status.activeRevisions` during upgrade (installed + those in progress)
* `Available` and `Progressing` conditions of an active, but not yet available revision, are listed under `.status.activeRevisions.conditions`
  so that can be easier to understand update issues

The new behavior is marked as experimental behind Boxcutter feature gate.

rashmigottipati