Add hpa v2beta2 to deprecation guide for v1.23

[reylejano]

This PR adds HorizontalPodAutoscaler autoscaling/v2beta2 API removal for Kubernetes v1.27.
autoscaling/v2beta2 API is deprecated in v1.23 as autoscaling/v2 reaches stable in v1.23

According to the HPA v2 to Stable KEP working document and the Kubernetes Deprecation Policy, autoscaling/v2beta2 must be supported for 9 months or 3 releases (which ever is longer) after the announced deprecation.

autoscaling/v2beta2 must be served in v1.24, v1.25, v1.26 and can be removed in v1.27

/cc @kubernetes/sig-autoscaling-pr-reviews @jlbutler @sftim
/assign @josephburnett @gjtempleton
/hold until lgtm from SIG Autoscaling

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

🔨 Explore the source changes: aba8166

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/61ad640a7ffd0800076103c0

[sftim]

I think some field names have been renamed(?)

[sftim]

BTW, https://github.com/kubernetes/enhancements/tree/master/keps/sig-autoscaling/2702-graduate-hpa-api-to-GA#renames is my basis for suspecting this.

[reylejano]

@josephburnett @gjtempleton , please confirm if there are field names renamed

[gjtempleton]

I believe this change ended up not happening due to the extra work that would have been required, see discussion here: https://github.com/kubernetes/kubernetes/pull/102534/files#r662447798

[sftim]

/lgtm
/approve

Leaving hold in place

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

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:

• content/en/OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: dc66ec050614a9ba6d5f39a6d5c0d4aea6a829bd

[sftim]

BTW, nothing stops us selecting and announcing a longer deprecation period (AFAIK). The one here is the guaranteed minimum.

[reylejano]

@gjtempleton can you confirm the removal of autoscaling/v2beta2 is targeted for v1.27

[gjtempleton]

@reylejano I don't think we've explicitly targetted removal for 1.27 in any of the docs around the promotion to GA, we only called out the timeline for the deprecation notices of v2beta1 and v2beta2, not the accompanying removal. As a side note, I realise the page being added to doesn't currently call out when we plan on stopping serving v2beta1 either.

@josephburnett would be best placed to speak to this, but I would be surprised if we didn't aim to remove these APIs as soon as possible under the deprecation policy.

[reylejano]

I'm considering closing this PR if there is no explicit target removal of the autoscaling/v2beta2 API

@sftim , what are your thoughts?

[sftim]

When we deprecate any built-in API we should publish a migration guide, even if we're unable to confirm when the removal is due.

[reylejano]

Looks like v2beta2 was added on May 21, 2018
Assuming the introduction of v2beta2 deprecated v2beta1. Since it's been more than 3 releases and more than 9 months since v2beta1 was deprecated, v2beta1 can be removed in any future release after 1.23.
I added the removal of v2beta1 to the deprecation guide under 1.24 as 1.24 is the earliest release v2beta1 can no longer be served at this point.

@josephburnett , please make any recommendations on the targeted removals of v2beta1 and v2beta2 and confirm if all existing persisted objects are accessible via autoscaling/v2 and if there are notable changes to add to the deprecation guide

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[reylejano]

@sftim , @gjtempleton , @josephburnett without a target release to remove v2beta1 and v2beta2, is this PR sufficient to merge to inform users the earliest release v2beta1 and v2beta2 can be removed?

[reylejano]

As we approach freezing k/website for the 1.23 release, I'm changing the target branch to main

[reylejano]

Closing since k/website is getting ready to be frozen for the 1.23 release tomorrow
Closing in favor of PR #30776 to main
/close

[k8s-ci-robot]

@reylejano: Closed this PR.

In response to this:

Closing since k/website is getting ready to be frozen for the 1.23 release tomorrow
Closing in favor of PR #30776 to main
/close

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.