From ad177b2e71cf36361a1d0280310257631699b68d Mon Sep 17 00:00:00 2001 From: James Strong Date: Mon, 14 Jun 2021 11:48:26 -0400 Subject: [PATCH] Update content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md Co-authored-by: Tim Bannister --- content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md b/content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md index a358b6d03a..b380b7a46b 100644 --- a/content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md +++ b/content/en/blog/_posts/2021-06-21-update-with-ingress-nginx.md @@ -8,7 +8,7 @@ slug: update-with-ingress-nginx **Authors:** James Strong, Ricardo Katz With all Kubernetes APIs, there is a process to creating, maintaining, and -ultimately deprecating them once they become GA. The networking.k8s.io API is no +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