Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.7.1
-
None
Description
Currently, NiFi is designed for static clusters, with frequent references in configuration files to a priori knowledge of node hostnames, ports, etc.
Efforts should be taken to make NiFi easier to dynamically scale. This can involve containerization improvements via Docker/rkt, deployment improvements via Kubernetes, and abstraction of the configuration values needed to stand up the cluster. A node should be able to join the cluster, and, given the correct keystore and truststore, immediately communicate with other existing nodes in the cluster without requiring direct configuration changes to them, or a restart of any node.
- authorizers.xml
- node identities
- permissions (RW on /proxy)
- ZooKeeper configuration
- etc.
Attachments
Issue Links
- depends upon
-
NIFI-5398 Identify cluster communication endpoints via combination of hostname and certificate rather than just certificate DN
- Open
- Is contained by
-
NIFI-5458 Improve NiFi TLS and certificate management
- Resolved
- is related to
-
NIFI-10975 Add Kubernetes Leader Election Manager and State Provider
- Resolved
- relates to
-
NIFI-5542 Add support for node groups to FileAccessPolicyProvider
- Resolved