Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to configure a specific hostname for notebook-controller generated VirtualServices #7528

Open
josh-thisisbud opened this issue Mar 26, 2024 · 1 comment

Comments

@josh-thisisbud
Copy link

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.

if err := unstructured.SetNestedStringSlice(vsvc.Object, []string{"*"}, "spec", "hosts"); err != nil {

@kubeflow-bot kubeflow-bot added this to To Do in Needs Triage Mar 26, 2024
@josh-thisisbud
Copy link
Author

Suggested fix at #7529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant