Ingress is only usable with root path "/"

[deschmih]

Hey,

I really like this project and it work with less effort in cluster. Thank's for that.
In cluster I use a nginx ingress controller and I have setup these controller in value.yaml like this:

...
ingress:
  enabled: true
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    nginx.ingress.kubernetes.io/use-regex: "true"
  hosts:
  - host: ""
    paths: 
    - /sew/octant-ui/(.*)
... 

See what happens:
Ingress is responding with HTTP_STATUS_CODE_OK,

but while accessing the octant-html-elements,

a wrong base-path is used.

Is there a way to fix this?
Thanks in advance.

Regards,
Michael

[aleveille]

Hi @deschmih, I will look into this. I am not sure this is possible because it is something Octant itself would have to support, and I don't remember seeing any proxy-specific settings. In any case, I'll look into it and I'll let you know.

[deschmih]

Hi @aleveille, are there some news about this topic? It would be nice to have this feature, otherwise I can't use octant in my application and that would be a shame. Thanks in advance.

[aleveille]

Hi @deschmih ! Sadly no I haven't had the chance to look at this. Hopefully I'll get the chance to look at this soon

[aleveille]

Hi @deschmih

I've had a look at this, and sadly I couldn't figure out how to do it (not in my limited time, anyway).

It looks like two internal flags could allow us to do this. However, this looks like it's not supported and not something they are aiming for in the near future (see issue #450 on their repo).

Nonetheless, if you can figure out how to properly use these flags to allow for a proxy path, I will consider adding support for that in the chart. Otherwise, I'll just have to close this issue.

octant -h
 [....]
      --proxy-frontend string          url to send frontend request to [DEV]
      --ui-url string                  dashboard url [DEV]