OPRUN-4691: Promote OLMLifecycleAndCompatibility feature gate to Default#2920
OPRUN-4691: Promote OLMLifecycleAndCompatibility feature gate to Default#2920perdasilva wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Hello @perdasilva! Some important instructions when contributing to openshift/api: |
📝 WalkthroughWalkthroughThis change enables Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold |
|
@perdasilva: This pull request references OPRUN-4691 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Enable the OLMLifecycleAndCompatibility feature gate in the Default feature set for SelfManaged clusters. Previously this gate was only enabled in TechPreviewNoUpgrade and DevPreviewNoUpgrade. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Per G. da Silva <pegoncal@redhat.com>
6fc0456 to
a1e80c1
Compare
|
@perdasilva: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
Summary
OLMLifecycleAndCompatibilityfeature gate in the Default feature set for SelfManaged clustersfeatures/features.go, generated feature gate manifests, andfeatures.mdNOTE
We're looking for an exception on the 5 test rule. The testing involves the building of a catalog image fixture that can be quite time consuming. Breaking the checks into individual tests and maintaining parallelism doesn't seem worth the expense. Other aspect of the CatalogSource are also already exercised by other tests.
Test plan
make verifypassesfeatures.md🤖 Generated with Claude Code