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

Beta APIs Are Off by Default #3136

Closed
5 tasks
deads2k opened this issue Jan 13, 2022 · 13 comments · Fixed by #3600
Closed
5 tasks

Beta APIs Are Off by Default #3136

deads2k opened this issue Jan 13, 2022 · 13 comments · Fixed by #3600
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone

Comments

@deads2k
Copy link
Contributor

deads2k commented Jan 13, 2022

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

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.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 13, 2022
@deads2k deads2k added the sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. label Jan 13, 2022
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 13, 2022
@liggitt liggitt added this to the v1.24 milestone Jan 19, 2022
@liggitt liggitt added the stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status label Jan 19, 2022
@gracenng gracenng added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 20, 2022
@rhockenbury
Copy link

rhockenbury commented Jan 20, 2022

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:

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

@liggitt
Copy link
Member

liggitt commented Feb 3, 2022

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

@rhockenbury
Copy link

rhockenbury commented Feb 3, 2022

Thanks! All set for enhancements freeze. 🚀

@mehabhalodiya
Copy link

mehabhalodiya commented Feb 12, 2022

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
Copy link

katcosgrove commented Feb 24, 2022

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
Copy link
Member

liggitt commented Feb 24, 2022

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
Copy link

salaxander commented Mar 21, 2022

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
Copy link

rhockenbury commented Mar 29, 2022

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

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented May 9, 2022

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! 🙂

manusa added a commit to manusa/yakc that referenced this issue May 9, 2022
Kubernetes 1.24 disables Beta APIs by default
kubernetes/enhancements#3136
manusa added a commit to manusa/yakc that referenced this issue May 9, 2022
Kubernetes 1.24 disables Beta APIs by default
kubernetes/enhancements#3136
@Priyankasaggu11929 Priyankasaggu11929 removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 9, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 7, 2022

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 6, 2022

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-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 6, 2022
@k8s-ci-robot k8s-ci-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 6, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Oct 6, 2022

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-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2022
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Oct 6, 2022

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
None yet
Development

Successfully merging a pull request may close this issue.