docs: FEATURE-GATES -> CONFIG-OPTIONS #827
Open
Conversation
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
Following community discussions, there's a desire to clarify the distinction between feature gates and config options. This update aligns the documentation with our intended direction for upcoming releases and avoids ambiguity. Note: Some internal structs still use the old terminology and are not updated in this commit. We plan to address those separately. Signed-off-by: Beraldo Leal <[email protected]>
|
@beraldoleal: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
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.
Following community discussions, there's a desire to clarify the distinction between feature gates and config options. This update aligns the documentation with our intended direction for upcoming releases and avoids ambiguity.
Note: Some internal structs still use the old terminology and are not updated in this commit. We plan to address those separately.
- Description for the changelog
We are updating our feature gates definition and from now on we are using the "config options" terminology. This will not change how users enable/disable features for this release, so probably we should not mention this change in the changelog.