-
Notifications
You must be signed in to change notification settings - Fork 835
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
Allow ambassador from other namespace to access SeldonDeployment #279
Comments
This makes sense. Will it work if Ambassador is running inside the namespace referred to? If so sounds like a great change. |
Hi @cliveseldon
Yes. It still works if Ambassador is running inside the same namespace.
Now port forward
Log of
|
Great. Looks ok then. |
Hi there,
ambassador
is a popular kubernetes-native API gateway. I would like to use anambassador
installed by k8s admin, which locates at a different namespace fromseldon-core
namespace, to route traffic to theSeldonDeployments
. This is to reduce the number ofambassadors
we install in the cluster.To support this feature, we can simply add
namespace
in the service annotation generated by Seldon cluster manager. I have manually tested this change and it works. E.g.This requires source code change at
https://github.com/SeldonIO/seldon-core/blob/master/cluster-manager/src/main/java/io/seldon/clustermanager/k8s/SeldonDeploymentOperatorImpl.java#L502-L519
Reference: https://www.getambassador.io/reference/mappings/#namespaces-and-mappings
Best,
Chenyuan
The text was updated successfully, but these errors were encountered: