K8s: make OLM distinction in limitation - #3975
Open
kaitlynmichael wants to merge 1 commit into
Open
Conversation
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at e139c8e |
|
hey @Kaitlyn Michael i personally would like to see this comment from the DOC ticket in there too
make it clear that its OperatorHub .. that means that the Operator is not upgradable from OperatorHub which is what people need to know. Is a workaround to not use OperatorHub and the CLI instead? Admiittedly most Openshift customers will want to use OperatorHub. Also just for clarification it is only 7.22.2-43 and not any 7.22.2 version before or after it right? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Note
Low Risk
Documentation-only wording change in release notes with no product or deployment behavior impact.
Overview
Clarifies the known limitation on the 7.22.2-43 → 8.0.20-26 upgrade path in the August 2026 release notes for both 7.22.2-43 and 8.0.20-26.
The bullet now states the direct upgrade is not supported in OLM-based deployments (instead of implying all deployment types), while keeping the same guidance to stay on 7.22.2-43 until a later 8.0.20 maintenance release.
Reviewed by Cursor Bugbot for commit e139c8e. Bugbot is set up for automated code reviews on this repo. Configure here.