This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 228
[cetic/helm-nifi] ingress path other than / doesn't work #22
Labels
bug
Something isn't working
Comments
Hello @RabbidDog, Thanks for your bug report, I was able to reproduce your bug. When the Maybe there is a configuration in nifi to use another path than /nifi. |
Thanks for the info. I will go through the docs and try to find a solution that works for me. |
So, we finally decided to use nifi in our cluster and figured out that the following changes in the values.yaml will do the trick:
for Traefik ingress controller
For Nginx ingress controller
|
Thanks for the explanation @RabbidDog ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
the application UI should be accessible though the custom ingress path
Version of Helm and Kubernetes:
helm: v2.14.3
kubernetes: v1.15.1
What happened:
the chart allows us to set the ingress.path variable. I would like to host the application at a path other than '/'. for e.g. at '/demo-nifi'. So I expected that setting ingress.path: '/demo-nifi' would work without additional changes i.e the application ui will be available at host/demo-nifi/nifi and all calls would be made to host/demo-nifi/{..}. But all REST calls from the browser assume that the urls are host/{..}
What you expected to happen:
ui uses custom path set in ingress.path
How to reproduce it (as minimally and precisely as possible):
set ingress.path: /demo-nifi
Anything else we need to know:
if forgive any ignorance about possible advanced configuration that can be done to resolve this issue
The text was updated successfully, but these errors were encountered: