You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 20, 2022. It is now read-only.
What did you expect to see?
I'm sure there are issues with our config and I'm not expecting it to work from the first time, but I was expecting at least to see pods being brought up and having some kind of errors in the Nifi logs.
What did you see instead? Under which circumstances?
No pods are being brought up and I see errors in the Nifi Operator
From what I understand the operator is looking for a secret named <cluster_name>-controller but I haven't referenced it anywhere I don't understand why it is looking for it
Bug Report
What did you do?
Deploy nifi secure nifi cluster without Cert-Manager deployed in my K8S cluster. Yaml used to test
The same YAML works for our insecure Nifi deployments just by removing
and setting
What did you expect to see?
I'm sure there are issues with our config and I'm not expecting it to work from the first time, but I was expecting at least to see pods being brought up and having some kind of errors in the Nifi logs.
What did you see instead? Under which circumstances?
No pods are being brought up and I see errors in the Nifi Operator
From what I understand the operator is looking for a secret named
<cluster_name>-controller
but I haven't referenced it anywhere I don't understand why it is looking for itEnvironment
0.7.1
btw, you should implemet --version command
Which ever version is included in your docker image - https://hub.docker.com/layers/orangeopensource/nifikop/v0.7.1-release/images/sha256-94eb3f1ec21f52041cc832fe9c1124cd6ad87666af8ffb41cd9173ae97f9a0c3?context=explore
v1.19.15-eks-9c63c4
Kubernetes cluster kind: EKS
NiFi version:
1.15.3
Possible Solution
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: