Skip to content
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-1965: add GA criterias APIServerIdentity #4067

Closed
wants to merge 2 commits into from
Closed
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions keps/prod-readiness/sig-api-machinery/1965.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
kep-number: 1965
beta:
approver: "@deads2k" # and @wojtek-t
stable:
approver: "@deads2k" # and @wojtek-t
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ Alpha should provide basic functionality covered with tests described above.

#### Beta -> GA Graduation

==TODO==
- support for aggregated apiservers
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@enj last I checked this was the biggest thing that was left for GA, anything else come to mind?


**For non-optional features moving to GA, the graduation criteria must include
[conformance tests].**
Expand Down
5 changes: 3 additions & 2 deletions keps/sig-api-machinery/1965-kube-apiserver-identity/kep.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -19,17 +19,18 @@ see-also:
- "https://docs.google.com/document/d/1ed7miqlFY7-9lZxE7gzoyx_MFQCtFEDqtcKMpaAmHys/edit?usp=sharing"

# The target maturity stage in the current dev cycle for this KEP.
stage: beta
stage: stable

# The most recent milestone for which work toward delivery of this KEP has been
# done. This can be the current (upcoming) milestone, if it is being actively
# worked on.
latest-milestone: "v1.26"
latest-milestone: "v1.28"

# The milestone at which this feature was, or is targeted to be, at each stage.
milestone:
alpha: "v1.20"
beta: "v1.26"
stable: "v1.28"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO this is not ready for stable - IIUC nothing actually uses this functionality, so we have no proof or experience that it actually works. GA graduation criteria should include at least one, ideally two plus usages of this feature (and those usages need to beta level).

The conversation around kubernetes/kubernetes#114314 (comment) happened so long ago that I have forgotten all the things that we need to fix.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO this is not ready for stable - IIUC nothing actually uses this functionality, so we have no proof or experience that it actually works. GA graduation criteria should include at least one, ideally two plus usages of this feature (and those usages need to beta level).

I think it's reasonable to say this feature shouldn't GA until StorageVersion API is Beta, which is currently the primary use-case for it. I'll add this to the GA criteria.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For posterity: UVIP is using this but is still in alpha.


# The following PRR answers are required at alpha release
# List the feature gate name and the components for which it must be enabled
Expand Down