-
currently no way to deploy to an authenticated and SSL-enabled NiFi instance. Should allow for a username/password to be supplied securely (env properties preferred, or prompt for interactive access)…
-
**Describe the bug**
trying to run nifi on eks version 1.19 all the pods are running and i can see in the logs that the server is up and running.
im using NGINX with aws internal load balancer.
…
-
**Describe the bug**
ca toolkit generated invalid keystore.jks properties
**Version of Helm and Kubernetes**:
helm Version:"v3.4.1
Kubernetes Version: 1.18.5
**What happened**:
Deployed …
-
**Describe the bug**
When I started celtic/nifi with replicationCount=# > 1, get error "Readiness probe failed: dial tcp 172.17.0.6:8080: connect: connection refused" and pods restarting itself over …
-
**Describe the problem**
hi i installed nifi and zookeeper on kubernetes cluster rke using helm
and im using nginx ingress controller
i can access web ui over https using ingress from outside t…
-
I am getting the below error:
ERROR [Timer-Driven Process Thread-1] c.g.w.nifi.processor.ProtobufDecoder ProtobufDecoder[id=299c2a4f-016a-1000-ffff-ffffab7ba612] No schema path given, please fill in …
-
Hey there,
I was just trying out the postgres tutorial and after creating a subscription I wanted to check the database. There was no schema "openiot", so I checked for the subscription. According …
-
oalam updated
7 years ago
-
Followed the instructions in the README.md file. Nifi won't start as there's no properties file found. NifiProperties.java expects the system property, PROPERTIES_FILE_PATH, to be set on startup. S…
-
## Bug Report
ArgoCD will never progress the health of Pod resources beyond Progressing when a Pod's restart policy is either never or onFailure. This is intentional as they assume Pods in this…