Skip to content

⚠️ OPRUN-4518: chore(Boxcutter): Rename ClusterExtensionRevision to ClusterObjectSet - #2589

Merged
openshift-merge-bot[bot] merged 1 commit into
operator-framework:mainfrom
camilamacedo86:rename-cer
Mar 30, 2026
Merged

⚠️ OPRUN-4518: chore(Boxcutter): Rename ClusterExtensionRevision to ClusterObjectSet#2589
openshift-merge-bot[bot] merged 1 commit into
operator-framework:mainfrom
camilamacedo86:rename-cer

Conversation

@camilamacedo86

Copy link
Copy Markdown
Contributor

No description provided.

CopilotAI review requested due to automatic review settings March 25, 2026 06:09
@netlify

netlifyBot commented Mar 25, 2026

Copy link
Copy Markdown

Deploy Preview for olmv1 ready!

NameLink
🔨 Latest commit88a025d
🔍 Latest deploy loghttps://app.netlify.com/projects/olmv1/deploys/69ca85ac36e3b3000823aa8e
😎 Deploy Previewhttps://deploy-preview-2589--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR renames the experimental Boxcutter “revision” CRD and its related plumbing from ClusterExtensionRevision to ObjectSet, updating the operator-controller codebase, Helm manifests/CRDs, apply-configurations, and e2e coverage to match the new API naming.

Changes:

  • Renames controller/applier code paths, constants, and types to ObjectSet (including Boxcutter reconciliation/status mirroring).
  • Updates Helm RBAC and experimental CRD manifests to use objectsets.olm.operatorframework.io.
  • Updates e2e steps/features and generated apply-configurations/docs to use ObjectSet.

Reviewed changes

Copilot reviewed 49 out of 51 changed files in this pull request and generated 1 comment.

Show a summary per file
FileDescription
test/e2e/steps/testdata/rbac-template-for-all-extensions.yamlUpdates RBAC resources/comments from clusterextensionrevisions to objectsets.
test/e2e/steps/testdata/pvc-probe-sa-boxcutter-rbac-template.yamlUpdates finalizer RBAC to objectsets/finalizers.
test/e2e/steps/testdata/olm-sa-boxcutter-rbac-template.yamlUpdates RBAC comment/resources to objectsets/finalizers.
test/e2e/steps/steps.goRenames step definitions and resource lookups to ObjectSet.
test/e2e/steps/hooks.goScenario context + cleanup updated to track/delete ObjectSets.
test/e2e/features/update.featureUpdates scenarios to assert ObjectSet conditions/archival.
test/e2e/features/status.featureUpdates revision-condition assertions to ObjectSet.
test/e2e/features/revision.featureRenames feature + scenarios for directly applying ObjectSet.
test/e2e/features/install.featureUpdates progress-deadline and annotation/label checks to ObjectSet.
test/e2e/README.mdUpdates ${CER_NAME} description to refer to ObjectSet.
internal/shared/util/test/artifacts.goCollects ObjectSet artifacts instead of ClusterExtensionRevision artifacts.
internal/operator-controller/labels/labels.goUpdates label/annotation docs to refer to ObjectSet.
internal/operator-controller/controllers/revision_engine_factory.goUpdates factory interface to accept *ocv1.ObjectSet.
internal/operator-controller/controllers/objectset_controller_test.goRenames reconciler tests/types to ObjectSet.
internal/operator-controller/controllers/objectset_controller_internal_test.goRenames internal controller tests/helpers to ObjectSet.
internal/operator-controller/controllers/objectset_controller.goRenames reconciler and RBAC markers to objectsets resources.
internal/operator-controller/controllers/common_controller_test.goUpdates condition type/reason constants used in tests.
internal/operator-controller/controllers/common_controller.goUpdates failure detection to use ObjectSet Progressing/Retrying.
internal/operator-controller/controllers/clusterextension_reconcile_steps.goUpdates comment referencing maintained revision storage to ObjectSet.
internal/operator-controller/controllers/boxcutter_reconcile_steps.goUpdates revision listing/sorting and condition mirroring to ObjectSet.
internal/operator-controller/applier/phase_test.goUpdates applyconfiguration types used in phase sorting tests.
internal/operator-controller/applier/phase.goRenames comparator + phase sorting to ObjectSet applyconfiguration types.
internal/operator-controller/applier/boxcutter_test.goUpdates generator expectations, retention const name, and mocks to ObjectSet.
internal/operator-controller/applier/boxcutter.goRenames generator interface/retention const and migrator/storage to ObjectSet.
helm/olmv1/templates/rbac/clusterrole-operator-controller-manager-role.ymlUpdates manager RBAC resources to objectsets (+status/+finalizers).
helm/olmv1/templates/crds/customresourcedefinition-objectsets.olm.operatorframework.io.ymlPoints Helm CRD template at objectsets CRD file.
helm/olmv1/base/operator-controller/crd/experimental/olm.operatorframework.io_objectsets.yamlCRD renamed/rewritten to define ObjectSet kind/plural/singular.
helm/olmv1/base/operator-controller/crd/experimental/olm.operatorframework.io_clusterextensions.yamlUpdates ClusterExtension CRD descriptions referencing active revisions to ObjectSets.
hack/tools/update-crds.shUpdates generated CRD filename variable to olm.operatorframework.io_objectsets.yaml.
docs/api-reference/olmv1-api-reference.mdUpdates API reference text to ObjectSet terminology.
docs/api-reference/crd-ref-docs-gen-config.yamlUpdates ignored types list to ObjectSet/ObjectSetList.
config/samples/olm_v1_clusterextension.yamlUpdates sample RBAC to objectsets/finalizers and comment text.
cmd/operator-controller/main.goUpdates cache/controller wiring to own/cache ocv1.ObjectSet.
applyconfigurations/utils.goReplaces ClusterExtensionRevision applyconfig mapping with ObjectSet mapping.
applyconfigurations/api/v1/revisionstatus.goUpdates comments/fields to reference ObjectSet.
applyconfigurations/api/v1/objectsetstatus.goAdds generated apply-configuration type for ObjectSetStatus.
applyconfigurations/api/v1/objectsetspec.goUpdates generated apply-configuration type for ObjectSetSpec.
applyconfigurations/api/v1/objectsetphase.goUpdates generated apply-configuration type for ObjectSetPhase.
applyconfigurations/api/v1/objectsetobject.goUpdates generated apply-configuration type for ObjectSetObject.
applyconfigurations/api/v1/objectset.goUpdates generated apply-configuration type for ObjectSet.
applyconfigurations/api/v1/clusterextensionstatus.goUpdates ClusterExtensionStatus applyconfig comments to reference ObjectSets.
applyconfigurations/api/v1/clusterextensionrevisionstatus.goRemoves generated ClusterExtensionRevisionStatus apply-configuration.
api/v1/zz_generated.deepcopy.goUpdates generated deepcopy implementations for ObjectSet types.
api/v1/validation_test.goUpdates validation tests to use ObjectSetSpec/ObjectSet.
api/v1/objectset_types_test.goRenames ObjectSet validity/immutability tests from ClusterExtensionRevision.
api/v1/objectset_types.goRenames the API type definitions/constants to ObjectSet.
api/v1/clusterextension_types.goUpdates ClusterExtension status/docs to reference ObjectSets.
AGENTS.mdUpdates repo documentation to name ObjectSet as the experimental revision CRD.
.claude/commands/list-e2e-steps.mdRenames step category from ClusterExtensionRevision to ObjectSet.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadinternal/shared/util/test/artifacts.go Outdated
@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

We can

/override go-apidif

The issues are expected
It is in techpreview

@openshift-ci

Copy link
Copy Markdown

@camilamacedo86: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • go-apidif

Only the following failed contexts/checkruns were expected:

  • Verify PR title
  • crd-diff
  • e2e
  • experimental-e2e
  • extension-developer-e2e
  • go-apidiff
  • go-verdiff
  • goreleaser
  • lint
  • netlify/olmv1/deploy-preview
  • st2ex-e2e
  • tide
  • unit-test-basic
  • upgrade-st2st-e2e
  • verify

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

We can

/override go-apidif

The issues are expected
It is in techpreview

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@codecov

codecovBot commented Mar 25, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 75.15723% with 79 lines in your changes missing coverage. Please review.
✅ Project coverage is 68.86%. Comparing base (7145047) to head (88a025d).
⚠️ Report is 2 commits behind head on main.

Files with missing linesPatch %Lines
api/v1/zz_generated.deepcopy.go60.31%25 Missing ⚠️
applyconfigurations/api/v1/clusterobjectset.go57.69%11 Missing ⚠️
applyconfigurations/utils.go0.00%10 Missing ⚠️
...plyconfigurations/api/v1/clusterobjectsetstatus.go0.00%8 Missing ⚠️
...troller/controllers/clusterobjectset_controller.go92.30%3 Missing and 5 partials ⚠️
internal/shared/util/test/artifacts.go0.00%8 Missing ⚠️
internal/operator-controller/applier/boxcutter.go92.85%3 Missing and 1 partial ⚠️
...plyconfigurations/api/v1/clusterobjectsetobject.go60.00%2 Missing ⚠️
cmd/operator-controller/main.go60.00%2 Missing ⚠️
...pplyconfigurations/api/v1/clusterobjectsetphase.go80.00%1 Missing ⚠️
Additional details and impacted files
@@ Coverage Diff @@## main #2589 +/- ##
=======================================
Coverage 68.86% 68.86% =======================================
Files 139 139 Lines 9872 9872 =======================================
Hits 6798 6798 Misses 2557 2557 Partials 517 517 
FlagCoverage Δ
e2e37.73% <6.66%> (+0.28%)⬆️
experimental-e2e52.43% <74.66%> (+0.02%)⬆️
unit53.51% <47.79%> (+0.01%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

We can

/override go-apidif/go-apidif

The issues are expected
It is in techpreview

@openshift-ci

Copy link
Copy Markdown

@camilamacedo86: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • go-apidif/go-apidif

Only the following failed contexts/checkruns were expected:

  • Verify PR title
  • crd-diff
  • e2e
  • experimental-e2e
  • extension-developer-e2e
  • go-apidiff
  • go-verdiff
  • goreleaser
  • lint
  • netlify/olmv1/deploy-preview
  • st2ex-e2e
  • tide
  • unit-test-basic
  • upgrade-st2st-e2e
  • verify

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

We can

/override go-apidif/go-apidif

The issues are expected
It is in techpreview

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

We can

/override api-diff-lint/api-diff-lint

The issues are expected
It is in techpreview

@openshift-ci

Copy link
Copy Markdown

@camilamacedo86: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • api-diff-lint/api-diff-lint

Only the following failed contexts/checkruns were expected:

  • Verify PR title
  • crd-diff
  • e2e
  • experimental-e2e
  • extension-developer-e2e
  • go-apidiff
  • go-verdiff
  • goreleaser
  • lint
  • netlify/olmv1/deploy-preview
  • st2ex-e2e
  • tide
  • unit-test-basic
  • upgrade-st2st-e2e
  • verify

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

We can

/override api-diff-lint/api-diff-lint

The issues are expected
It is in techpreview

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

We can

/override api-diff-lint

The issues are expected
It is in techpreview

@openshift-ci

Copy link
Copy Markdown

@camilamacedo86: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • api-diff-lint

Only the following failed contexts/checkruns were expected:

  • Verify PR title
  • crd-diff
  • e2e
  • experimental-e2e
  • extension-developer-e2e
  • go-apidiff
  • go-verdiff
  • goreleaser
  • lint
  • netlify/olmv1/deploy-preview
  • st2ex-e2e
  • tide
  • unit-test-basic
  • upgrade-st2st-e2e
  • verify

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

We can

/override api-diff-lint

The issues are expected
It is in techpreview

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

/override go-apidiff

@openshift-ci

Copy link
Copy Markdown

@camilamacedo86: Overrode contexts on behalf of camilamacedo86: go-apidiff

Details

In response to this:

/override go-apidiff

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

/label api-diff-lint-override

@openshift-ci

Copy link
Copy Markdown

@camilamacedo86: The label(s) /label api-diff-lint-override cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label api-diff-lint-override

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@tmshort

tmshort commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

Is there a ticket associated with this (OPRUN-4518)?

@tmshorttmshort changed the title ⚠️ chore(Boxcutter): Rename ClusterExtensionRevision to ObjectSet⚠️ OPRUN-4518: chore(Boxcutter): Rename ClusterExtensionRevision to ObjectSetMar 25, 2026
@tmshort

Copy link
Copy Markdown
Contributor

The /override command only works for non-required tests.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

@tmshort

Thank you for looking on that.
Regards:

Is there a ticket associated with this (OPRUN-4518)?

Yes, it is the ticket.

@camilamacedo86

Copy link
Copy Markdown
ContributorAuthor

@perdasilva@pedjak@dtfranz

We have this task to finish boxcutter
Could you please help us out get this merged?

@openshift-ciopenshift-ciBot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 27, 2026
CopilotAI review requested due to automatic review settings March 30, 2026 10:29
tmshort pushed a commit to tmshort/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
tmshort pushed a commit to tmshort/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
tmshort pushed a commit to tmshort/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 1, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 2, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 2, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 2, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 2, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 4, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 4, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 7, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 7, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 8, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 8, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 9, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 9, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 9, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 9, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 11, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 11, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 11, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 11, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 14, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 14, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 15, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 15, 2026
…s ClusterObjectSet
The upstream rename of ClusterExtensionRevision to ClusterObjectSet
(operator-framework/operator-controller#2589) breaks the incompatible
operator detection in cluster-olm-operator. The cluster-olm-operator
binary still reads ClusterExtensionRevision resources to find operators
with olm.maxOpenShiftVersion, so after the rename it never detects
incompatible operators and InstalledOLMOperatorsUpgradeable stays True.
Skip this test when NewOLMBoxCutterRuntime feature gate is enabled
until cluster-olm-operator is updated to read ClusterObjectSet.
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
openshift-bot pushed a commit to openshift-bot/operator-framework-operator-controller that referenced this pull request Apr 16, 2026
…t in OTE tests
Update all remaining references to ClusterExtensionRevision in
openshift/tests-extension to use ClusterObjectSet, matching the
upstream rename in operator-framework/operator-controller#2589.
Files updated:
- test/qe/specs/olmv1_ce.go: RBAC resource names and comments
- test/olmv1-preflight.go: scenario constants, test names, RBAC rules
- .openshift-tests-extension/openshift_payload_olmv1.json: test name
- pkg/bindata/qe/bindata.go: embedded RBAC templates
- test/qe/testdata/olm/sa-nginx-limited-boxcutter.yaml: RBAC resources
- test/qe/testdata/olm/sa-nginx-insufficient-operand-rbac-boxcutter.yaml: RBAC resources
Signed-off-by: Camila Macedo <cmacedo@redhat.com>
Made-with: Cursor
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api-diff-lint-overrideapprovedIndicates a PR has been approved by an approver from all required OWNERS files.go-apidiff-overridelgtmIndicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@camilamacedo86@tmshort@perdasilva@pedjak