search

cetic / helm-nifi

Helm Chart for Apache Nifi
Apache License 2.0
215 stars 228 forks source link

[cetic/nifi] issue title Nifi is deployed successfully. but unable to access nifi UI. #241

Closed pawankbh closed 2 years ago

pawankbh commented 2 years ago

Nifi is deployed successfully. but unable to access nifi UI.

image

pawankbh commented 2 years ago

image

gforeman02 commented 2 years ago

@pawankbh try adding 10.124.13.73:8443 (including port) to properties.webProxyHost value.

fzhan commented 2 years ago

@pawankbh try adding 10.124.13.73:8443 (including port) to properties.webProxyHost value.

This should be a dynamic value since a new pod would use a new IP address.

What's the most effective way? https://community.cloudera.com/t5/Support-Questions/NiFi-1-5-System-Error-Invalid-host-header/td-p/195175

fzhan commented 2 years ago

@pawankbh try adding 10.124.13.73:8443 (including port) to properties.webProxyHost value.

This should be a dynamic value since a new pod would use a new IP address.

What's the most effective way? https://community.cloudera.com/t5/Support-Questions/NiFi-1-5-System-Error-Invalid-host-header/td-p/195175

wknickless commented 2 years ago

@fzhan properties.webProxyHost should be set to the name(s) you expect your users to type into their web browser.

For example, see https://github.com/wknickless/helm-nifi/blob/feature/cert-manager/tests/07-oidc-cluster-values.yaml , where properties.webProxyHost is set to the DNS name of the Ingress that fronts the NiFi cluster.

github-actions[bot] commented 2 years ago

This issue is stale because it has not seen recent activity. Remove stale label or comment or this will be closed.