Add note about v1beta2 removal

kubernetes · Jan 7, 2025 · a193b1a · a193b1a
1 parent d3ee257
commit a193b1a
Showing 1 changed file with 4 additions and 5 deletions.
diff --git a/vertical-pod-autoscaler/docs/installation.md b/vertical-pod-autoscaler/docs/installation.md
@@ -4,7 +4,7 @@
 
 - [Installation](#installation)
   - [Compatibility](#compatibility)
-  - [Notice on deprecation of v1beta2 version (>=0.13.0)](#notice-on-deprecation-of-v1beta2-version-0130)
+  - [Notice on removal of v1beta2 version (>=1.3.0)](#notice-on-removal-of-v1beta2-version-130)
   - [Notice on removal of v1beta1 version (>=0.5.0)](#notice-on-removal-of-v1beta1-version-050)
   - [Prerequisites](#prerequisites)
   - [Install command](#install-command)
@@ -61,11 +61,10 @@ kubectl delete clusterrole system:vpa-status-actor
 kubectl delete clusterrolebinding system:vpa-status-actor
 ```
 
-## Notice on deprecation of v1beta2 version (>=0.13.0)
+## Notice on removal of v1beta2 version (>=1.3.0)
 
-**NOTE:** In 0.13.0 we deprecate `autoscaling.k8s.io/v1beta2` API. We plan to
-remove this API version. While for now you can continue to use `v1beta2` API we
-recommend using `autoscaling.k8s.io/v1` instead. `v1` and `v1beta2` APIs are
+**NOTE:** In 1.3.0 we disabled the old version of the API - `autoscaling.k8s.io/v1beta2`.
+We recommend using `autoscaling.k8s.io/v1` instead. `v1` and `v1beta2` APIs are
 almost identical (`v1` API has some fields which are not present in `v1beta2`)
 so simply changing which API version you're calling should be enough in almost
 all cases.