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] Graduate HPA API to GA #2702

Closed
4 tasks
supriya-premkumar opened this issue May 10, 2021 · 21 comments · Fixed by #3180
Closed
4 tasks

[KEP] Graduate HPA API to GA #2702

supriya-premkumar opened this issue May 10, 2021 · 21 comments · Fixed by #3180
Assignees
Labels
sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status

Comments

@supriya-premkumar
Copy link
Contributor

supriya-premkumar commented May 10, 2021

Enhancement Description

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 May 10, 2021
@supriya-premkumar
Copy link
Contributor Author

/sig autoscaling

@k8s-ci-robot k8s-ci-robot added sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 10, 2021
@supriya-premkumar supriya-premkumar changed the title [KEP] Graduate v2beta2 Autoscaling API to GA [KEP] Graduate Autoscaling API to GA May 10, 2021
@supriya-premkumar
Copy link
Contributor Author

supriya-premkumar commented May 10, 2021

Initial PR: #2703

@josephburnett
Copy link
Member

/assign josephburnett

@supriya-premkumar supriya-premkumar added this to the v1.22 milestone May 11, 2021
@supriya-premkumar supriya-premkumar added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 11, 2021
@JamesLaverack JamesLaverack added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 11, 2021
@JamesLaverack JamesLaverack removed this from the v1.22 milestone May 11, 2021
@JamesLaverack
Copy link
Member

Hey 👋 1.22 Enhancements Lead here,

If you'd like to have this issue tracked for 1.22, You'll need to ask a SIG Autoscaling lead (cc @gjtempleton @mwielgus) to add it to the "KEP Collection" tab of the enhancements tracking sheet and we can track it from there.

Let me know if you have any questions.

@sftim
Copy link
Contributor

sftim commented May 12, 2021

Promotes autoscaler API resource v2beta2 version to GA

Is it more accurate to say:

Promote HorizontalPodAutoscaler API resource v2beta2 version to GA

?
(avoiding confusion with, eg, cluster autoscaler, MultidimPodAutoscaler, VerticalPodAutoscaler).

@supriya-premkumar supriya-premkumar changed the title [KEP] Graduate Autoscaling API to GA [KEP] Graduate HPA API to GA May 13, 2021
@JamesLaverack
Copy link
Member

/milestone v1.22

@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone May 14, 2021
@JamesLaverack JamesLaverack added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 14, 2021
@PI-Victor
Copy link
Member

Hello @supriya-premkumar 👋, 1.22 Docs release lead here.
This enhancement is marked as ‘Needs Docs’ for 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

@salaxander salaxander added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Aug 19, 2021
@salaxander
Copy link
Contributor

Hi @supriya-premkumar - Could you open a PR on the KEP to mark it as implemented? We can close out the issue then :)

Thanks!

@gjtempleton
Copy link
Member

Hi @salaxander - thanks for the follow-up! This KEP had its target moved to 1.23 so isn't yet implemented.

@gjtempleton
Copy link
Member

@supriya-premkumar Could you update the description's target release to 1.23 please?

@salaxander
Copy link
Contributor

/milestone v1.23

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.22, v1.23 Sep 3, 2021
@salaxander salaxander added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 3, 2021
@jlbutler
Copy link

Hi @supriya-premkumar 👋 1.23 Docs release lead here.

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

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 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!

@supriya-premkumar
Copy link
Contributor Author

Hi @jlbutler,
cc'ing @josephburnett for more info/context on this one.

@gracenng
Copy link
Member

gracenng commented Nov 9, 2021

Hi @josephburnett , 1.23 Enhancements Shadow here.

In light of code freeze on November 16th, please link the code PR related to this enhancement in the description so the release team can track it. As of now, the status of this enhancement is at-risk.

Please feel free to ping me once the code PR's are merged.

@salaxander
Copy link
Contributor

@josephburnett - can you confirm if all k/k PRs for this KEP have merged?

@josephburnett
Copy link
Member

Yes! All the core PRs have landed. Primarily kubernetes/kubernetes#102534 and two followup PRs (kubernetes/kubernetes#106315 and kubernetes/kubernetes#106316). We still need doc updates I think, but we have another week for that, right?

@sftim
Copy link
Contributor

sftim commented Nov 17, 2021

Placeholder doc PRs are due tomorrow AIUI, and should be ready for review on the 23rd
https://www.kubernetes.dev/resources/release/

@chrisnegus
Copy link

Hi @josephburnett 👋 1.23 Docs shadow here.

As @sftim mentioned, docs PR placeholders for 1.23 are due tomorrow.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo.
Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.
Thanks!

@josephburnett
Copy link
Member

@chrisnegus @sftim here is my placeholder PR: kubernetes/website#30547

@chrisnegus
Copy link

Excellent! Thanks @josephburnett

@gracenng
Copy link
Member

gracenng commented Jan 9, 2022

Hi @josephburnett ,

1.24 Enhancements Lead here. Could you please update this enhancements's KEP status to implemented, then close this issue?

Thanks :)

@gracenng gracenng removed this from the v1.23 milestone Jan 9, 2022
@gracenng gracenng removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. 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.