@sig-network @conformance @release-1.19

Feature: Ingress class

Ingresses can be implemented by different controllers, often with different configuration. Each Ingress definition could specify a class, a reference to an IngressClass resource that contains additional configuration including the name of the controller that should implement the class. https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class

Scenarios

Status	Progress
Passed	100.00%
Failed	0.00%

Scenario: An Ingress with an invalid ingress class should not send traffic to the matching backend service

Given 5s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test-ingress-class
spec:
  ingressClassName: some-invalid-class-name
  rules:
    - host: "ingress-class"
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: ingress-class-prefix
                port:
                  number: 8080

Then 5m0s The Ingress status should not contain the IP address or FQDN

Duration: 5m5s

Kubernetes ingress controller conformance