Tweak documentation formating about deprecated apiVersion
values. (#7663)
* Tweak documentation formating about deprecated `apiVersion` values. * retweak after rebase
This commit is contained in:
parent
9acf62d867
commit
15385c6d56
1 changed files with 3 additions and 2 deletions
|
@ -63,11 +63,12 @@ FIELDS:
|
|||
|
||||
There are 2 reasons primarily.
|
||||
|
||||
(Reason #1) Until K8s version 1.21, it was possible to create a ingress resource, with the "apiVersion:" field set to a value like ;
|
||||
(Reason #1) Until K8s version 1.21, it was possible to create a ingress resource, with the "apiVersion:" field set to a value like:
|
||||
|
||||
- extensions/v1beta1
|
||||
- networking.k8s.io/v1beta1
|
||||
|
||||
(You would get a message about deprecation but the ingress resource would get created.)
|
||||
You would get a message about deprecation but the ingress resource would get created.
|
||||
|
||||
From K8s version 1.22 onwards, you can ONLY set the "apiVersion:" field of a ingress resource, to the value "networking.k8s.io/v1". The reason is [official blog on deprecated ingress api versions](https://kubernetes.io/blog/2021/07/26/update-with-ingress-nginx/).
|
||||
|
||||
|
|
Loading…
Reference in a new issue