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 2022-01-27 02:53:51 +00:00
parent 8f106d8db3
commit 92e9800623
5 changed files with 54 additions and 54 deletions
Download patch file Download diff file Expand all files Collapse all files

2
index.html
View file

@ -29,7 +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></p> <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> <h3 id=reason-1>Reason #1<a class=headerlink href=#reason-1 title="Permanent link"></a></h3> <p>Until K8s version 1.21, it was possible to create an Ingress resource using deprecated versions of the Ingress API, such as:</p> <ul> <li><code>extensions/v1beta1</code></li> <li><code>networking.k8s.io/v1beta1</code></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 <strong>only</strong> access the Ingress API via the stable, <code>networking.k8s.io/v1</code> API. The reason is explained in the <a href=https://kubernetes.io/blog/2021/07/26/update-with-ingress-nginx/ >official blog on deprecated ingress API versions</a>.</p> <h3 id=reason-2>Reason #2<a class=headerlink href=#reason-2 title="Permanent link"></a></h3> <p>If you are already using the Ingress-NGINX controller and then upgrade to K8s version v1.22 , there are several scenarios where your existing Ingress objects will not work how you expect. 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><code>ingressClassName</code> is a field in the specs of an Ingress object.</p> <p><div class=highlight><pre><span></span><code>kubectl explain ingress.spec.ingressClassName
</code></pre></div></p> <h2 id=what-has-caused-this-change-in-behavior>What has caused this change in behavior?<a class=headerlink href=#what-has-caused-this-change-in-behavior title="Permanent link"></a></h2> <p>There are 2 reasons primarily.</p> <h3 id=reason-1>Reason #1<a class=headerlink href=#reason-1 title="Permanent link"></a></h3> <p>Until K8s version 1.21, it was possible to create an Ingress resource using deprecated versions of the Ingress API, such as:</p> <ul> <li><code>extensions/v1beta1</code></li> <li><code>networking.k8s.io/v1beta1</code></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 <strong>only</strong> access the Ingress API via the stable, <code>networking.k8s.io/v1</code> API. The reason is explained in the <a href=https://kubernetes.io/blog/2021/07/26/update-with-ingress-nginx/ >official blog on deprecated ingress API versions</a>.</p> <h3 id=reason-2>Reason #2<a class=headerlink href=#reason-2 title="Permanent link"></a></h3> <p>If you are already using the Ingress-NGINX controller and then upgrade to K8s version v1.22 , there are several scenarios where your existing Ingress objects will not work how you expect. 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><code>ingressClassName</code> is a field in the specs of an Ingress object.</p> <p><div class=highlight><pre><span></span><code>kubectl explain ingress.spec.ingressClassName
</code></pre></div> <div class=highlight><pre><span></span><code><span class=go>KIND: Ingress</span>
<span class=go>VERSION: networking.k8s.io/v1</span>