Beta APIs Are Off by Default

[deads2k]

trafficstars

Beta APIs Are Off by Default

• New beta APIs will not be enabled in clusters by default. Existing beta APIs and new versions of existing beta APIs, will continue to be enabled by default.
• Kubernetes Enhancement Proposal:
• Discussion Link:
• Primary contact (assignee): @deads2k
• Responsible SIGs: sig-architecture
• Enhancement target (which target equals to which milestone): 1.24
• [ ] Stable
  • [ ] KEP (k/enhancements) update PR(s):
    • [ ] https://github.com/kubernetes/enhancements/pull/3137
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update(s):

This is a policy KEP, so it will start as Stable.

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[rhockenbury]

Hi @deads2k! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze at 18:00pm PT on Thursday Feb 3rd. This enhancement is targeting stable for 1.24.

Here’s where this enhancement currently stands:

• [x] Updated KEP file using the latest template has been merged into the k/enhancements repo. - INCLUDED IN PR #3137
• [x] KEP status is marked as implementable for latest-milestone: 1.24 - INCLUDED IN PR #3137
• [ ] KEP has a test plan section filled out. - INCLUDED IN PR #3137
• [x] KEP has up to date graduation criteria. - NOT REQUIRED AS INDICATED IN PR #3137
• [x] KEP has a production readiness review that has been completed and merged into k/enhancements. - INCLUDED IN PR #3137

Please plan to merge #3137 before enhancements freeze. The status of this enhancement is at risk. Thanks!

[liggitt]

@rhockenbury the KEP is merged. Can you verify this is in good shape for 1.24?

[rhockenbury]

Thanks! All set for enhancements freeze. 🚀

[mehabhalodiya]

Hi @deads2k 👋🏻 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

[katcosgrove]

Hey there! Comms shadow here. Would y'all like to have this included in the deprecations and removal blog for 1.24? Here's what it looked like for 1.22: https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/

[liggitt]

Would y'all like to have this included in the deprecations and removal blog for 1.24?

no, this doesn't modify any existing beta APIs, it is strictly for future beta APIs.

[salaxander]

Hey @deads2k and @liggitt - Are there any k/k or other PRs we should be tracking for 1.24 code freeze for this one?

[rhockenbury]

Hi @deads2k. Was k/k#107993 the only PR needed for this KEP for v1.24?

[Priyankasaggu11929]

Hello @deads2k 👋, 1.25 Enhancements team here.

This feature has been fully implemented and is now GA in K8s version 1.24. 🎉

Please update the kep.yaml file's status to implemented and close this issue.

This would help accurate tracking in the v1.25 cycle. Thank you so much! 🙂

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.