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

Beginne damit nachzuverfolgen, wie der Operator die Überschreibungen in nifi.properties für HTTP/HTTPS, die Ingress-Health-Checks und den Kubernetes Service verarbeitet. Reproduziere das Problem mit der 0.6.0-Konfiguration auf k3s und überprüfe anschließend, dass die UI über Ingress erreichbar ist und die Health-Checks erfolgreich sind, wenn HTTP ausgewählt ist.