Hi Fugui! There is no need to restart the nodes. You should use a properly filled authorizers.xml for the initial cluster nodes only. Then as you add new nodes you should use an authorizers.xml that is "empty" meaning it has no nodes and users in it, neither the initial admin defined in the policy and user providers. If you do this the node will inherit authorizations configuration from the existing nodes. The trick is, that then you have to add the new node on the UI manually and grant read/write proxy permissions for it as well.
Peter On Sun, Sep 23, 2018 at 5:23 AM 笑对人生 <446513...@qq.com> wrote: > Hi , > I've encountered some problems when I deploy a secure nifi cluster in > Kubernetes,. Could you help me analyze my problems? > Can nifi cluster which enabled SSL be scaled without reboot in > kubernetes? > When I add a new node to a secure nifi cluster in kubernetes, do I need > to modify the authorizers.xml file for each node? > Whether each node needs to maintain a mapping of host name and domain > name in /etc/hosts file? > https://github.com/AlexsJones/kubernetes-nifi-cluster/issues/2 How can > this problem be solved? > Look forward to your reply! Thank you for your time. > Regards, > Fugui
