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

Update content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md

Browse Source 
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
James Strong
2021-06-14 11:52:50 -04:00
committed by GitHub
parent 939f7d0c80
commit efafee8ee0
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md
+9 -4
View File
@@ -9,10 +9,15 @@ slug: update-with-ingress-nginx
With all Kubernetes APIs, there is a process to creating, maintaining, and
ultimately deprecating them once they become GA. The networking.k8s.io API group is no
different. With the release of Kubernetes 1.22, The networking.k8s.
io/v1beta1 API version of IngressClass will no longer be served in
Kubernetes v1.22. The extensions/v1beta1 and networking.k8s.io/v1beta1 API
versions of Ingress also will no longer be served in v1.22. This move has been
different. The upcoming Kubernetes 1.22 release will remove several deprecated APIs
that are relevant to networking:
- the `networking.k8s.io/v1beta1` API version of [IngressClass](/docs/concepts/services-networking/ingress/#ingress-class)
- all beta versions of [Ingress](/docs/concepts/services-networking/ingress/): `extensions/v1beta1` and `networking.k8s.io/v1beta1`
On a v1.22 Kubernetes cluster, you'll be able to access Ingress and IngressClass
objects through the stable (v1) APIs, but access via their beta APIs won't be possible.
This change has been in
in discussion since
[2017](https://github.com/kubernetes/kubernetes/issues/43214),
[2019](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) with