whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify deprecated API versions and releases (#16403)

Browse Source
This commit is contained in:
Jordan Liggitt
2019-09-17 12:30:24 -04:00
committed by Kubernetes Prow Robot
parent 48d73a6443
commit 67c20b3d37
1 changed files with 14 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2019-07-18-some-apis-are-being-deprecated.md
+14 -23
View File
@@ -10,32 +10,23 @@ slug: api-deprecations-in-1-16
As the Kubernetes API evolves, APIs are periodically reorganized or upgraded. As the Kubernetes API evolves, APIs are periodically reorganized or upgraded.
When APIs evolve, the old API is deprecated and eventually removed. When APIs evolve, the old API is deprecated and eventually removed.
The 1.16 release will deprecate APIs for four services: The **v1.16** release will stop serving the following deprecated API versions in favor of newer and more stable API versions:
* NetworkPolicy * NetworkPolicy (in the **extensions/v1beta1** API group)
* PodSecurityPolicy * Migrate to use the **networking.k8s.io/v1** API, available since v1.8.
* DaemonSet, Deployment, StatefulSet, and ReplicaSet Existing persisted data can be retrieved/updated via the **networking.k8s.io/v1** API.
* Ingress * PodSecurityPolicy (in the **extensions/v1beta1** API group)
* Migrate to use the **policy/v1beta1** API, available since v1.10.
Existing persisted data can be retrieved/updated via the **policy/v1beta1** API.
* DaemonSet, Deployment, StatefulSet, and ReplicaSet (in the **extensions/v1beta1** and **apps/v1beta2** API groups)
* Migrate to use the **apps/v1** API, available since v1.9.
Existing persisted data can be retrieved/updated via the **apps/v1** API.
None of these resources will be removed from Kubernetes or deprecated in any way. The **v1.20** release will stop serving the following deprecated API versions in favor of newer and more stable API versions:
However, to continue using these resources, you must use a current version of
the Kubernetes API.
# Migration Details * Ingress (in the **extensions/v1beta1** API group)
* Migrate to use the **networking.k8s.io/v1beta1** API, serving Ingress since v1.14.
* NetworkPolicy: will no longer be served from **extensions/v1beta1** in **v1.16**. Existing persisted data can be retrieved/updated via the **networking.k8s.io/v1beta1** API.
* Migrate to the networking.k8s.io/v1 API, available since v1.8. Existing persisted
data can be retrieved/updated via the networking.k8s.io/v1 API.
* PodSecurityPolicy: will no longer be served from **extensions/v1beta1** in **v1.16**.
* Migrate to the policy/v1beta1 API, available since v1.10. Existing persisted
data can be retrieved/updated via the policy/v1beta1 API.
* DaemonSet, Deployment, StatefulSet, and ReplicaSet: will no longer be served
from **extensions/v1beta1**, **apps/v1beta1**, or **apps/v1beta2** in **v1.16**.
* Migrate to the apps/v1 API, available since v1.9. Existing persisted data
can be retrieved/updated via the apps/v1 API.
* Ingress: will no longer be served from **extensions/v1beta1** in **v1.18**.
* Migrate to the networking.k8s.io/v1beta1 API, serving Ingress since v1.14.
Existing persisted data can be retrieved/updated via the networking.k8s.io/v1beta1 API.
# What To Do # What To Do