IngressClass¶

Overview¶

The chart automatically creates an IngressClass resource when the ingress library is enabled and the cluster exposes networking.k8s.io/v1/IngressClass (available since Kubernetes 1.19, below the chart's 1.21 minimum).

For ingress class filtering (controlling which Ingress resources the controller watches), see Configuration.

Configuration¶

ingressClass:
  enabled: true       # Create IngressClass (default: true)
  name: haptic        # IngressClass name (default: haptic, avoids conflict with other HAProxy controllers)
  default: false      # Mark as cluster default
  controllerName: haproxy-haptic.org/controller

The default name is haptic (not haproxy) so the chart can be installed alongside other HAProxy-based ingress controllers without colliding on IngressClass. When replacing an existing controller, override ingressClass.name to match your incumbent's class (often haproxy) and your existing Ingress manifests keep working.

Capability detection¶

The chart uses Capabilities.APIVersions.Has to check for networking.k8s.io/v1/IngressClass. Because IngressClass reached v1 in Kubernetes 1.19 and the chart's minimum is 1.21, this API is always present on a supported cluster, so the check never skips creation in practice. It's an internal safety net that only skips the resource on clusters below the supported floor, where the API is absent.

Creation conditions¶

IngressClass is created only when both of the following are true:

ingressClass.enabled: true (default)
controller.templateLibraries.ingress.enabled: true (default)

A third, internal condition also applies: the networking.k8s.io/v1/IngressClass API must exist in the cluster. On any supported cluster (1.21+) this is always the case, so it isn't something you need to plan for; it only skips creation below the supported floor. See Capability detection.

Multi-Controller Environments¶

When running multiple ingress controllers:

Ensure unique identification:

# Controller 1 (haptic)
ingressClass:
  name: haptic
  controllerName: haproxy-haptic.org/controller

# Controller 2 (nginx)
ingressClass:
  name: nginx
  controllerName: k8s.io/ingress-nginx

Only one should be default:

# Set default on one controller only
ingressClass:
  default: true  # Only on ONE controller

Disabling IngressClass Creation¶

If you manage IngressClass resources separately or use an external tool:

ingressClass:
  enabled: false

Using IngressClass¶

Ingress resources reference the IngressClass via spec.ingressClassName:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example
spec:
  ingressClassName: haptic  # References IngressClass.metadata.name
  rules:
    - host: example.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: example-service
                port:
                  number: 80