Open kamniphat01 opened 7 months ago
Why would you want to use your own HTTPS vault server?
The NiFi newest version of the NiFi chart communicates internally over HTTPS; it's obligatory since NiFi version 1.16.3. If you want to deploy NiFi in cluster mode using your chart and share the certificates over the different nodes, the easiest way to do that is by using an external cert-manager instance or by using the nifi nifi-tls-toolkit as an init-container for your pods.
I serve NiFi externally over HTTPS by using an ingress-nginx-controller with an SSL certificate, and internally with cert-manager and it works great!
Hi Guys, need some help or suggestion.
Helmchart 1.1.3 Nifi Image version: 1.19.1 Standalone Nifi Server: Replica 1
Currently i am trying to figure out which part of the scripts or helmchart that generate the truststore and keystore and replace in nifi.properties
Default from helmchart nifi.properties
After the deployment checked in container /conf/nifi.properties![image](https://github.com/cetic/helm-nifi/assets/77826553/2cfc4bc2-da3d-4bf1-96a6-98500060822a)
Objective is to update in bootstrap-hashicorp-vault.conf and get update the keystore password and truststore password same as nifi.properties for enabled the TLS to connect to my HTTPS vault server instead of HTTP.
Not recommended to use StandardSSLContextService for manual input keystore pwd & truststore pwd due to sometimes the Nifi server restart it will regenerate a new keystore pwd and truststore pwd.