Deprecated APIs Removed In Kubernetes 1.16

Deprecated APIs Removed In Kubernetes 1.16

  • August 4, 2019
Table of Contents

Deprecated APIs Removed In Kubernetes 1.16

As the Kubernetes API evolves, APIs are periodically reorganized or upgraded. When APIs evolve, the old API is deprecated and eventually removed. The 1.16 release will deprecate APIs for four services: None of these resources will be removed from Kubernetes or deprecated in any way.

However, to continue using these resources, you must use a current version of the Kubernetes API. NetworkPolicy: will no longer be served from extensions/v1beta1 in v1.16.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. Existing persisted data can be retrieved/updated via the networking.k8s.io/v1beta1 API.

Source: kubernetes.io

Tags :
Share :
comments powered by Disqus

Related Posts

33(+) Kubernetes security tools

33(+) Kubernetes security tools

Kubernetes image scanning Kubernetes runtime security Kubernetes network security Image distribution and secrets management Kubernetes security audit End-to-end commercial security tools Join our live session to learn more! Kubernetes security tools … there are so freaking many of them; with different purposes, scopes and licenses. That’s why we decided to create this Kubernetes security tools list, including open source projects and commercial platforms from different vendors, to help you choose the ones that look more interesting to you and guide you in the right direction depending on your Kubernetes security needs.

Read More
How a Production Outage Was Caused Using Kubernetes Pod Priorities

How a Production Outage Was Caused Using Kubernetes Pod Priorities

Read More
Future of CRDs: Structural Schemas

Future of CRDs: Structural Schemas

CustomResourceDefinitions were introduced roughly two years ago as the primary way to extend the Kubernetes API with custom resources. From the beginning they stored arbitrary JSON data, with the exception that kind, apiVersion and metadata had to follow the Kubernetes API conventions. In Kubernetes 1.8 CRDs gained the ability to define an optional OpenAPI v3 based validation schema.

Read More