Remove v1beta2 API

[jbartosik]

Follow up to #4969, remove the deprecated API.

Beta API versions must be supported for 9 months or 3 releases (whichever is longer) after deprecation

Deprecation was in VPA 0.13.0, which was released on 2023-02-03; In the mean time we had VPA 0.14.0.

So the next VPA can't drop the API yet (it will be 3rd one). We also need to wait at least until 2023-11-03 before dropping the API.

So likely the release triggered by K8s 1.28 in August keeps the API.

And the release triggered by K8s 1.29 can drop it.

[Shubham82]

Any update on this issue, as current k8s version is k8s v1.31and v1beta2 API (with depricated message) is still present in vpa-v1-crd-gen.yaml file.

[Shubham82]

cc @jbartosik @voelzmo @kwiesmueller

[voelzmo]

Agreed, we should be able to drop this now and document that the new release won't work with k8s versions < v1.29

[raywainman]

SGTM

[adrianmoisey]

Agreed, we should be able to drop this now and document that the new release won't work with k8s versions < v1.29

Isn't the removal of the CRD/API related to the VPA version and not the Kubernetes version?

[raywainman]

We've been trying to release a VPA version roughly every k8s minor version so that's likely what Joachim was meaning here.

[adrianmoisey]

We've been trying to release a VPA version roughly every k8s minor version so that's likely what Joachim was meaning here.

Oh interesting, I never knew that.
Since that's not a promise we make to users (directly or indirectly) I'd suggest that the communication about deprecation references which version of the VPA drops support, not which versions of Kubernetes drop support.