Validate Helm Ingress Configuration

Ingress Configuration Validation

The ingress section in Helm charts controls external HTTP/HTTPS access to your services. With the transition from Ingress v1beta1 to v1, the configuration requirements have become stricter.

Standard Pattern

ingress:
  enabled: true
  className: nginx
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
  hosts:
    - host: app.example.com
      paths:
        - path: /
          pathType: Prefix
    - host: api.example.com
      paths:
        - path: /v1
          pathType: Prefix
        - path: /v2
          pathType: Prefix
  tls:
    - secretName: app-tls
      hosts:
        - app.example.com
        - api.example.com

What Gets Validated

1. pathType values: Must be one of ImplementationSpecific, Exact, or Prefix. This field is required in Ingress v1.
2. Type checks: ingress.enabled should be boolean, hosts and tls should be arrays, annotations should be an object.
3. Structure: Each host entry should have host (string) and paths (array).

pathType Reference

pathType	Behavior
ImplementationSpecific	Matching depends on the IngressClass controller
Exact	Matches the URL path exactly (case-sensitive)
Prefix	Matches based on a URL path prefix split by /

Common Mistakes

Missing pathType (required in Ingress v1):

paths:
  - path: /
    # pathType missing - API will reject this

Wrong pathType value:

paths:
  - path: /api
    pathType: prefix  # Must be "Prefix" (capital P)

Boolean annotation values not quoted:

annotations:
  nginx.ingress.kubernetes.io/ssl-redirect: true
  # Should be "true" (string) - YAML boolean may cause issues