Support switch to non-TLS UI

Affected version

nifi-operator-0.6.0

Current and expected behavior

Current behavior

1. defaults
   When using Nifi in a default setting, I fail to establish an ingress properly exposing the Nifi UI to the outside, probably because Nifi is set to use httpS/8443.

2. with overrides
   When providing overriding Nifi settings to use http/8080

configOverrides:
   nifi.properties:
     nifi.web.https.host: ""
     nifi.web.https.port: ""
     nifi.web.http.host: "0.0.0.0"
     nifi.web.http.port: "8080"
     nifi.cluster.protocol.is.secure: "false"

the ingress is working, but Nifi is unstable because health checks (still assuming 8443) are always failing.

Expected behavior

There's a supported way to use Ingress with the Nifi UI with health checks succeeding.

Bonus

Operator recognizes http/https and will set up a k8s Service accordingly.

Possible solution

No response

Additional context

off-topic: trying to open a feature request led to a 404 for me.

Environment

k3s

Would you like to work on fixing this bug?

No response

Commencez par retracer la manière dont l’opérateur gère les remplacements de nifi.properties pour HTTP/HTTPS, les vérifications de santé d’Ingress et le Kubernetes Service. Reproduisez le problème avec la configuration 0.6.0 sur k3s, puis vérifiez que l’UI est accessible via Ingress et que les vérifications de santé réussissent lorsque HTTP est sélectionné.