Hi Kenneth, Suggestions for our documentation are always welcome. The best approach would be to first file a JIRA [1] (there is a self service portal to request an account there if you don't have one already), and then file a Pull Request in Github (from your fork of the repo). The file you'd want to update, I assume, is here [2]. Another option, is also to attach a patch file to the JIRA if you're ok with that and someone else can open a Pull Request with the changes.
As a side note, we recently merged a change to completely decouple NiFi and the Zookeeper option (for state management and leader election) [3], so good to make all of this even more obvious in the docs. [1] https://issues.apache.org/jira/browse/NIFI [2] https://github.com/apache/nifi/blob/main/nifi-docs/src/main/asciidoc/administration-guide.adoc [3] https://issues.apache.org/jira/browse/NIFI-14921 Hope this helps, Pierre Le jeu. 4 sept. 2025 à 22:31, Ken Bass <ken.b...@ikedainnovations.com.invalid> a écrit : > > All concerned, > > I'd like to suggest a change/update to the administrator's guide. I'm in the > process of deprecating ZooKeeper used in conjunction with a NiFi deployment > on Kubernetes. There is a line in the admin guide that suggests that > ZooKeeper is the default and only cluster-wide state mangager. However, this > directly conflicts with the above section that touches on Kubernetes > ConfigMaps being a viable alternative. I'm happy to utilize whatever path is > currently in place to update this documentation if necessary. > > Very respectfully, > Kenneth Bass
