Ingress — NiFi

With ingress.enabled=true, HTTP access to NiFi uses the host configured in ingress.rules[0].host. The UI path is /nifi. In test environments a sample hostname is commonly used (e.g., nifi.local); in production use a FQDN that your DNS resolves.

Prerequisites

• Ingress Controller (e.g., class nginx).
• A Service that exposes the NiFi UI (generally the external service defined in nifiCluster.externalServices; the chart's default name is tdp-service-ip-nifi).

Example

The exact structure may vary with the package version; confirm with helm show values. In general terms:

ingress:
  enabled: true
  ingressClassName: nginx
  rules:
    - host: <ingress-host>
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: <nifi-external-service-name>
                port:
                  number: 8080

Replace <ingress-host> with a hostname you control. <nifi-external-service-name> must match the name in nifiCluster.externalServices (chart default: tdp-service-ip-nifi).

URL

http://<ingress-host>/nifi

Troubleshooting

Issue	Solution
502 / no backend	Check the Service name/port and whether the NiFi pods are ready
Host does not resolve	DNS or local resolution for <ingress-host>
Ingress not created	Set ingress.enabled: true in the values

Controller-specific annotations (e.g., rewrite-target) depend on the Ingress you use; configure them according to your cluster's documentation.