-
Notifications
You must be signed in to change notification settings - Fork 150
OCPBUGS-57129: Add missing Console capability annotation #992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add this annotation to
include.release.openshift.io/hypershiftcluster-profile manifests, because openshift/hypershift#6183 is still in flight trying to make "HyperShift clusters withConsoledisabled" an option.However, this particular manifest also belongs to other cluster profiles, like the default
include.release.openshift.io/self-managed-high-availability. You cannot add theConsolecapability annotation to those, because there are alreadyself-managed-high-availabilityclusters with theConsoledisabled and the cluster-version operator actively managing this resource. Upon update, the CVO will implicitly enable theConsolecapability, to avoid orphaning that resource. There's OTA-1039 thinking that some day, we might grow some kind of knob to work around that, but there hasn't been enough interest to get it prioritized. So for today's CVO, you'd need to shard this manifest into two:include.release.openshift.io/hypershiftwhere you knew there couldn't be anyConsole-less clusters yet, where you could add thisConsoleannotation.include.release.openshift.io/self-managed-high-availabilitywhere there might be existingConsole-less clusters, where you need to either live with the presence of the resource on clusters withoutConsoleenabled, or find some other workaround.Also in this space, the
include.release.openshift.io/single-node-developerprofile was abandoned, so you can drop that (e.g. see openshift/cluster-version-operator#685)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may want to just focus on the Deployment in this pull, and have this StorageVersionMigration manifest be part of OCPBUGS-57055.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi :) why was it decided to merge this PR with this change?
Aren’t we agreed it's needed to keep the profiles separate?