DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deploy GitHub Pages

Browse source
This commit is contained in:
k8s-ci-robot 2021-09-26 17:49:22 +00:00
parent 24461f05f6
commit 888ac30db9
4 changed files with 53 additions and 54 deletions
Download patch file Download diff file Expand all files Collapse all files

3
index.html
View file

@ -29,8 +29,7 @@ FIELDS:
spec <Object>
Spec is the desired state of the IngressClass. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status`
</code></pre></div> <h2 id=what-has-caused-this-change-in-behaviour>What has caused this change in behaviour ?<a class=headerlink href=#what-has-caused-this-change-in-behaviour title="Permanent link"></a></h2> <p>There are 2 reasons primarily.</p> <p>(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</p> <div class=highlight><pre><span></span><code>(You would get a message about deprecation but the ingress resource would get created.)
</code></pre></div> <p>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 <a href=https://kubernetes.io/blog/2021/07/26/update-with-ingress-nginx/ >official blog on deprecated ingress api versions</a>.</p> <p>(Reason #2) When you upgrade to K8s version v1.22, while you are already using the Ingress-NGINX controller, there are several scenarios where the old existing ingress objects will not work. Read this FAQ to check which scenario matches your use case.</p> <h2 id=what-is-ingressclassname-field>What is ingressClassName field ?<a class=headerlink href=#what-is-ingressclassname-field title="Permanent link"></a></h2> <p>ingressClassName is a field in the specs of a ingress object.</p> <p><div class=highlight><pre><span></span><code>% k explain ingress.spec.ingressClassName
</code></pre></div> <h2 id=what-has-caused-this-change-in-behaviour>What has caused this change in behaviour ?<a class=headerlink href=#what-has-caused-this-change-in-behaviour title="Permanent link"></a></h2> <p>There are 2 reasons primarily.</p> <p>(Reason #1) Until K8s version 1.21, it was possible to create a ingress resource, with the "apiVersion:" field set to a value like:</p> <ul> <li>extensions/v1beta1</li> <li>networking.k8s.io/v1beta1</li> </ul> <p>You would get a message about deprecation but the ingress resource would get created.</p> <p>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 <a href=https://kubernetes.io/blog/2021/07/26/update-with-ingress-nginx/ >official blog on deprecated ingress api versions</a>.</p> <p>(Reason #2) When you upgrade to K8s version v1.22, while you are already using the Ingress-NGINX controller, there are several scenarios where the old existing ingress objects will not work. Read this FAQ to check which scenario matches your use case.</p> <h2 id=what-is-ingressclassname-field>What is ingressClassName field ?<a class=headerlink href=#what-is-ingressclassname-field title="Permanent link"></a></h2> <p>ingressClassName is a field in the specs of a ingress object.</p> <p><div class=highlight><pre><span></span><code>% k explain ingress.spec.ingressClassName
KIND: Ingress
VERSION: networking.k8s.io/v1