-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP-4578: Server Feature Gate in etcd #4610
Conversation
siyuanfoundation
commented
May 2, 2024
- One-line PR description: KEP to introduce feature gate in etcd
- Issue link: Server Feature Gate in etcd #4578
- Other comments:
/sig etcd cc @serathius @ahrtr @logicalhan @jmhbnz @fuweid @stackbaek @henrybear327 @wenjiaswe |
5e3a2db
to
9e23e71
Compare
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.
Thanks for getting this started team. We have already had some discussions on this at KubeCon etc so overall intention makes sense to me.
Two minor questions below from my first read.
f229b14
to
e621249
Compare
d281e40
to
161b03d
Compare
* the new feature would need to be enabled by default to always apply the bug fix for new releases. | ||
* it changes the API which is not desirable in patch version releases. | ||
|
||
The proper way of handling these bug fixes should be: |
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.
I like this, but we should get some feedback from K8s folks. cc @wojtek-t @logicalhan
Some small nits, but overall proposal looks good to me. |
- "@jmhbnz" | ||
- "@wenjiaswe" | ||
- "@fuweid" | ||
- "@logicalhan" |
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.
That's a lot of reviewers, no need to have so many people, but if you want to keep it please make sure that you got review from everyone listed.
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.
ok. I'll try to get their reviews.
Signed-off-by: Siyuan Zhang <[email protected]>
/lgtm thanks! |
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.
/lgtm
Great work team.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmhbnz, serathius, siyuanfoundation The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| Alpha | Same as [Kubernetes feature stages - Alpha feature](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-stages): <ul><li>Disabled by default. </li><li>Might be buggy. Enabling the feature may expose bugs. </li><li>Support for feature may be dropped at any time without notice. </li><li>The API may change in incompatible ways in a later software release without notice. </li><li>Recommended for use only in short-lived testing clusters, due to increased risk of bugs and lack of long-term support.</li></ul> | Before moving a feature to Beta, it should have <ul><li> Full unit/integration/e2e/robustness test coverage.</li><li>Full performance benchmark/test if applicable.</li><li> No significant changes for at least 1 minor release.</li></ul> | | ||
| Beta | Same as [Kubernetes feature stages - Beta feature](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-stages) except etcd Beta feature does not allow incompatible schema change: <ul><li>Enabled by default. </li><li>The feature is well tested. Enabling the feature is considered safe.</li><li>Support for the overall feature will not be dropped, though details may change.</li><li>Recommended for only non-business-critical uses because of potential for discovering new hard-to-spot bugs through wider adoption.</li></ul> | Before moving a feature to GA, it should have <ul><li> Widespread usage.</li><li>No bug reported for at least 1 minor release.</li></ul> | |
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.
Minor comment:
- For Alpha -> Beta, should add Criteria:
No unresolved major bugs
. - For Beta -> GA, update criteria:
No major bug reported for at least 1 minor release
Note they are just minimal Graduation Criteria.
Overall looks good to me. Thanks @siyuanfoundation for driving the effort. |
LGTM. Thanks @siyuanfoundation ! |