Open StathisKap opened 9 months ago
Do you mean HTTP:200 with internal server error? The good news is that your NiFi deployment is working perfectly, it's just your ingress that isn't resolving to the correct service ('/nifi'), which is why you get the error (or I used to at least 😄)
You're serving nifi on a non literal ip ("nifi.mlx.institute".example.com). You have to specify the desired host using both the ingress.host field & the properties.webProxyHost field, like this:
properties:
webProxyHost: "${var.host_nifi}"
ingress:
enabled: true
hosts:
- ${var.host_nifi}
This way NiFi will proxy the connections to that host to the literal ip of the nifi service running in your cluster.
Describe the bug Ingress doesn't work no matter what I do. Port forwarding does. I've got cert-manager on my k3s cluster with traefik, and whether I add it with letsencrypt through annotations and the tls block or use the cert-manager options below, it doesn't allow connection. It always keeps on saying, Internal Server Error
Version of Helm, Kubernetes and the Nifi chart:
helm version
k3s -version
helm list
What happened: Ingress keeps causing Internal Server Error
What you expected to happen: To just get access to the front end
How to reproduce it (as minimally and precisely as possible): Use these values
Here are some information that help troubleshooting:
values.yaml
or the changes made to the default one (after removing sensitive information)Check if a pod is in error:
Inspect the pod, check the "Events" section at the end for anything suspicious.