Michael H

> After further investigations with the help of @juldrixx we are not sure that the option `nifi.security.autoreload.enabled` is enough to apply new certificates. If any of you has an exemple...

> > > After further investigations with the help of @juldrixx we are not sure that the option `nifi.security.autoreload.enabled` is enough to apply new certificates. If any of you has...

Thank you for spending the time to track this down. That makes sense. It looks like Jetty has a unit test that specifically handles symlink targets. I wonder if it's...

Yeah perhaps we can still pursue node restarts and make that a flag as a part of the SSL config. Then it wouldn't matter what NiFi version the operator is...

> Is it worth looking at replacing the `nifi.properties` logic we have here, to make use of the ENV scripts in `apache/nifi`'s docker image instead? My worry with using templates...

I should give two examples. I believe it can be an either/or. So you'd configure either: ```yaml apiVersion: nifi.konpyutaika.com/v2alpha1 kind: NifiCluster metadata: name: nifi-cluster spec: stateManagement: zookeeper: zkPath: /my-cluster zkAddress:...

This is an interesting idea and i definitely understand the desire for the feature. I'm wondering if this is something the operator should just do by default without needing a...

> > This is an interesting idea and i definitely understand the desire for the feature. I'm wondering if this is something the operator should just do by default without...

I don't know what you mean by health check paths? Are you referring to ingress path URIs?

This appears to be the same scenario discussed in the slack: https://konpytika.slack.com/archives/C0362VBRM24/p1702911625342399 Please make sure your CRDs are updated to the v1.6.0 version. Primary indicator was: > Umar Hussain [1...