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
Hey there, I'm running into an issue where Istio is preferring to route traffic to other cluster components due to them being more specific with their configured hostnames.
E.g. A request to dave.example.com/notebooks/dave/etc is preferring to go to a VS with host: dave.example.com, path: / than the generated virtualservice with host: ['*'], path: /notebooks/dave/etc
I would like to be able to expose my notebooks in a similar way, however I find that the hostname value is hardcoded into this service.
Hey there, I'm running into an issue where Istio is preferring to route traffic to other cluster components due to them being more specific with their configured hostnames.
E.g. A request to
dave.example.com/notebooks/dave/etc
is preferring to go to a VS withhost: dave.example.com, path: /
than the generated virtualservice withhost: ['*'], path: /notebooks/dave/etc
I would like to be able to expose my notebooks in a similar way, however I find that the hostname value is hardcoded into this service.
kubeflow/components/notebook-controller/controllers/notebook_controller.go
Line 499 in bd7f250
The text was updated successfully, but these errors were encountered: