IngressClass resource fields and annotations
The IngressClass resource is a class of Ingress resources supporting simultaneous use of multiple ingress controllers, e.g., Application Load Balancer and NGINX. Each IngressClass resource specifies a distinct ingress controller. This enables traffic routing across multiple Ingress resources of different controllers within the same application and Managed Service for Kubernetes cluster.
Tip
We recommend using the new Yandex Cloud Gwin controller instead of an ALB Ingress controller and Gateway API.
When using multiple ingress controllers, explicitly declare the target controller for each Ingress resource. To do this, specify the relevant controller’s IngressClass in the spec.ingressClassName field.
IngressClass is a standard Kubernetes resource. We describe its fields and annotations below. For more information on configuring and using IngressClass resources, see this Kubernetes guideIngress resources and routing traffic using multiple ingress controllers.
IngressClass
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata: <ObjectMeta>
spec:
controller: <string>
|
Field |
Value / Type |
Description |
|
|
|
This is a required field. Kubernetes API version. |
|
|
|
Resource type |
|
|
|
This is a required field. |
|
|
|
This is a required field. Resource specification. |
|
|
|
This is a required field. Ingress controller name specified by the
|
Example
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
labels:
app.kubernetes.io/component: controller
name: alb
annotations:
ingressclass.kubernetes.io/is-default-class: "true"
spec:
controller: ingress.alb.yc.io/yc-alb-ingress-controller
ObjectMeta
name: <string>
labels:
<string>: <string>
annotations:
ingressclass.kubernetes.io/is-default-class: "<bool>"
|
Field |
Value / Type |
Description |
|
|
|
This is a required field. Resource name. For more information about the format, see this Kubernetes guide This name is also specified in the spec.ingressClassName field of the |
|
|
|
Kubernetes metrics for managing and monitoring Kubernetes objects. We recommend |
|
|
|
Resource annotations. The available annotation is |