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

Inizia tracciando il modo in cui l’operatore gestisce gli override di nifi.properties per HTTP/HTTPS, gli health check di Ingress e il Kubernetes Service. Riproduci il problema con la configurazione 0.6.0 su k3s, quindi verifica che la UI sia raggiungibile tramite Ingress e che gli health check abbiano esito positivo quando è selezionato HTTP.