docs(feature gates): updates the feature gates content #11097
Merged
+66
−179
Conversation
This file contains 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
Signed-off-by: prmellor <[email protected]>
scholzj
reviewed
Jan 30, 2025
documentation/modules/operators/ref-operator-cluster-feature-gates.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/operators/ref-operator-cluster-feature-gates.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/operators/ref-operator-cluster-feature-gates.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/operators/ref-operator-cluster-feature-gates.adoc
Outdated
Show resolved
Hide resolved
Comment on lines
20
to
25
| Check the xref:ref-operator-cluster-feature-gates-{context}[Strimzi feature gate releases]. | ||
| If a feature gate is enabled, you may need to disable it before downgrading. | ||
| If the feature gate is permanently enabled, you may need to first downgrade to a version where it can still be disabled. | ||
|
|
||
| Kafka clusters managed by Strimzi always use node pools. | ||
| Downgrading to a cluster without node pools is not possible. |
There was a problem hiding this comment.
I'm not sure I would understand as a user what to look for and what to do about it to be honest. I would expect this to have a more clear information about the particular feature gates and their upgrade/downgrade limitations.
I would either remove it completely right now or leave some generic statement that sometimes, feature gates might need to be disabled when upgrading / downgrading. But that right now there is nothing special like that..
There was a problem hiding this comment.
I think it might be useful to reassure the user that they don't need to worry about feature gates at the moment, so I've adjusted the statement.
documentation/modules/upgrading/proc-upgrade-cluster-operator.adoc
Outdated
Show resolved
Hide resolved
Signed-off-by: prmellor <[email protected]>
ppatierno
approved these changes
Feb 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Documentation
Updates the feature gates content.
Removes outdated and replicated content.
Consolidates the content into a single file.
For graduated features (GA), we now say refer to the docs when they were introduced for information.
Checklist
Please go through this checklist and make sure all applicable tasks have been done