nifi-registry service never respond if via k8s port-forwarding about charts HOT 4 CLOSED

Hello @chwongeric ,
use this

# Additional environment variables to set
extraEnvs:
  - name: NIFI_REGISTRY_WEB_HTTP_HOST
    value: "0.0.0.0"

/opt/nifi-registry/scripts/start.sh

# Establish baseline properties
prop_replace 'nifi.registry.web.http.port'      "${NIFI_REGISTRY_WEB_HTTP_PORT:-18080}"
prop_replace 'nifi.registry.web.http.host'      "${NIFI_REGISTRY_WEB_HTTP_HOST:-$HOSTNAME}"

from charts.

After further investigation, I see nifi-registry-0 pod always serving in nifi-registry-0:18080 instead of 0.0.0.0:18080 because immutable config file conf/nifi-registry.properties in container has this line: nifi.registry.web.http.host=nifi-registry-0

thus nifi-registry-0 can not accept from localhost: so http://nifi-registry-0:18080/nifi-registry works but not http://localhost:18080/nifi-registry. suspect this is the reason k8s port-forward always failed to reach nifi-registry.

Could you please share the tips to overwrite conf/nifi-registry.properties in this https://github.com/cetic/helm-nifi/ chart which point to https://github.com/dysnix/charts ? Thank you very much!

condition: registry.enabled
name: nifi-registry
repository: https://dysnix.github.io/charts/
version: 0.3.2

nifi@nifi-registry-0:/opt/nifi-registry$ tail -f ./nifi-registry-current/logs/nifi-registry-app.log
...
2021-10-22 05:19:53,856 INFO [main] org.eclipse.jetty.server.Server Started @16735ms
2021-10-22 05:19:53,857 INFO [main] o.apache.nifi.registry.jetty.JettyServer NiFi Registry has started. The UI is available at the following URLs:
2021-10-22 05:19:53,857 INFO [main] o.apache.nifi.registry.jetty.JettyServer http://nifi-registry-0:18080/nifi-registry # <-- Note: not localhost or 0.0.0.0
2021-10-22 05:19:53,868 INFO [main] o.apache.nifi.registry.BootstrapListener Successfully initiated communication with Bootstrap

nifi@nifi-registry-0:/opt/nifi-registry/nifi-registry-current$ cat conf/nifi-registry.properties | grep http
nifi.registry.web.http.host=nifi-registry-0
nifi.registry.web.http.port=18080
nifi.registry.web.https.host=
nifi.registry.web.https.port=

nifi@nifi-registry-0:/opt/nifi-registry/nifi-registry-current$ curl -v http://nifi-registry-0:18080/nifi-registry

• Trying 100.96.1.232...
• TCP_NODELAY set
• Expire in 200 ms for 4 (transfer 0x55da291e8f50)
• Connected to nifi-registry-0 (100.96.1.232) port 18080 (#0)

GET /nifi-registry HTTP/1.1
Host: nifi-registry-0:18080
User-Agent: curl/7.64.0
Accept: /

< HTTP/1.1 302 Found
< Date: Mon, 08 Nov 2021 01:33:21 GMT
< Location: http://nifi-registry-0:18080/nifi-registry/
< Content-Length: 0
< Server: Jetty(9.4.19.v20190610)
nifi@nifi-registry-0:/opt/nifi-registry/nifi-registry-current$ curl -v http://localhost:18080/nifi-registry

• Trying 127.0.0.1...
• TCP_NODELAY set
• Expire in 149999 ms for 3 (transfer 0x5582d17bff50)
• Expire in 200 ms for 4 (transfer 0x5582d17bff50)
• connect to 127.0.0.1 port 18080 failed: Connection refused
• Trying ::1...
• TCP_NODELAY set
• Expire in 149999 ms for 3 (transfer 0x5582d17bff50)
• Immediate connect fail for ::1: Cannot assign requested address
• Trying ::1...
• TCP_NODELAY set
• Expire in 149999 ms for 3 (transfer 0x5582d17bff50)
• Immediate connect fail for ::1: Cannot assign requested address
• Failed to connect to localhost port 18080: Connection refused
• Closing connection 0
  curl: (7) Failed to connect to localhost port 18080: Connection refused

from charts.

@jirimedved , thank you very much for reply! I think this tip should work than current relay approach via socat.

BTW, wondering if I can also ask for git branch support for nifi-registry's values.yaml? I tried to add branch name like - branch: 'develop' but no luck, all flow files always write to master branch instead. How do I use specific branch with nifi-registry in values.yaml? thanks a lot!

flowProvider:
  git:
    enabled: true
    url: 'https://user:[email protected]/developers/nifi_flows'
    remote: 'origin'
    branch: 'develop'
    user: 'user'
    password: 'passwd'

from charts.

closing current issue and created another issue https://github.com/dysnix/charts/issues/131 for git branch

from charts.