Open a4tarasiuk opened 2 years ago
Is there any progress on this? It is kind of a show stopper as we cannot configure our initial admin user to setup more users. I can see everything going into the authorizers.temp, just not making it to the authorizers.xml.
@jjjedlicka you might try the version I've submitted under PR #218 ; it includes GitHub action tests that confirm the initial admin can be used. And leave a comment about how it works for you, whether it works or fails. If that works for you, please let @banzo and @zakaria2905 know over at the comment section of PR #218 so they can feel more comfortable merging it. Or if it doesn't work for you definitely leave me a comment over there so I can make a test for your use case and get it working.
@wknickless we are using version: 1.0.6, appVersion: 1.14.0. I am somewhat new to helm, but it looks like the check-in is the cert manager branch. How do I pull in a branch that is not part of the helm application version or available chart versions?
@jjjedlicka you should be able to do something like:
git clone https://github.com/wknickless/helm-nifi.git helm-nifi
cd helm-nifi
git checkout 2bb07f92bc2d74f8f6e0be1efe038b2147444dda
helm dep update
helm install nifi . -f /path/to/my-local-nifi-values-file.yaml
Describe the bug After installation, user is not able to authorize. Unknown identity error. After chart installation,
conf/authorization.xml
does not have information about users.usersGroupProvider
section does not contain k8s user, and admin user that is set invalues.yaml
.Everything works fine on 0.7.8 version. I think that something wrong with volumes, because in previous version of chart, i was able to update
users.xml
file and others, and after reinstallation, they persisted, but currently every file is overwritten.Version of Helm, Kubernetes and the Nifi chart: Helm: 3.6.2
Kubernetes: 1.19.7
Nifi chart: 1.0.0
What happened: After not being able to authorize, I checked
authorizers.xml
file and found that it does not contain my user email as initial user identity and k8s user too.authorizers.xml
section innifi-config
configmap is valid, and also is present in authorizers.temp, butauthorizers.xml
has some default info.What you expected to happen: Currently in authorizers.xml i have:
I expect (took from 0.7.8 version):
Also the same case with
users.xml
file, instead of k8s user and my user, i have defaultJohn
user.How to reproduce it (as minimally and precisely as possible):
helm upgrade --install nifi -f values.yaml cetic/nifi -n nifi
Anything else we need to know:
values.yaml
:Check if a pod is in error:
Inspect the pod, check the "Events" section at the end for anything suspicious.
Get logs on a failed container inside the pod (here the
server
one):