{"config":{"lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Welcome \u00b6 This is the documentation for the NGINX Ingress Controller. It is built around the Kubernetes Ingress resource , using a ConfigMap to store the NGINX configuration. Learn more about using Ingress on k8s.io . Getting Started \u00b6 See Deployment for a whirlwind tour that will get you started. FAQ - Migration to apiVersion networking.k8s.io/v1 \u00b6 Please read this official blog on deprecated ingress api versions If you are using ingress objects in your pre K8s v1.22 cluster, and you upgrade to K8s v1.22, then this document may be relevant to you. Please read this official documentation on the IngressClass object What is an ingressClass and why is it important for users of Ingress-NGINX controller now ? \u00b6 IngressClass is a Kubernetes resource. See the description below. Its important because until now, a default install of the Ingress-NGINX controller did not require a ingressClass object. But from version 1.0.0 of the Ingress-NGINX Controller, a ingressclass object is required. On clusters with more than one instance of the Ingress-NGINX controller, all instances of the controllers must be aware of which Ingress object they must serve. The ingressClass field of a ingress object is the way to let the controller know about that. _$ k explain ingressClass KIND: IngressClass VERSION: networking.k8s.io/v1 DESCRIPTION: IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class. FIELDS: apiVersion <string> APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources kind <string> Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata 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` What has caused this change in behaviour ? \u00b6 There are 2 reasons primarily. (Reason #1) Until K8s version 1.21, it was 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.) From K8s version 1.22 onwards, you can ONLY set the \"apiVersion:\" field of a ingress resource, to the value \"networking.k8s.io/v1\".Thereasonisofficialblogondeprecatedingressapiversions.(Reason#2)WhenyouupgradetoK8sversionv1.22,whileyouarealreadyusingtheIngress-NGINXcontroller,thereareseveralscenarioswheretheoldexistingingressobjectswillnotwork.ReadthisFAQtocheckwhichscenariomatchesyourusecase.WhatisingressClassNamefield?\u00b6ingressClassNameisafieldinthespecsofaingressobject.%kexplainingress.spec.ingressClassNameKIND:IngressVERSION:networking.k8s.io/v1FIELD:ingressClassName<string>DESCRIPTION:IngressClassNameisthenameoftheIngressClassclusterresource.TheassociatedIngressClassdefineswhichcontrollerwillimplementtheresource.Thisreplacesthedeprecated`kubernetes.io/ingress.class`annotation.Forbackwardscompatibility,w
