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
Yes you are correct. We had both before but as the operator is clusterwide by default at present then the namespace is needed to ensure no clashes. We should update the docs.
Should the Ambassador REST endpoint docs mention the namespace in which a model is deployed, or am I missing something here?
To reproduce:
The Ambassador REST docs at https://docs.seldon.io/projects/seldon-core/en/v0.3.1/workflow/serving.html state:
If, as an example, I deploy a model on minikube following https://github.com/SeldonIO/seldon-core/blob/v0.3.1/examples/models/mlflow_model/mlflow.ipynb and port-forward using
kubectl port-forward $(kubectl get pods -l app.kubernetes.io/name=ambassador -o jsonpath='{.items[0].metadata.name}') 8003:8080
then the namespace seems to be needed in the REST endpoint path: i.e. predictions are accessible via
If I deploy the same mlflow-example model into a "seldon" namespace (loosely following https://github.com/SeldonIO/seldon-core/blob/v0.3.1/notebooks/helm_examples.ipynb), then the model predictions are accessible via
Both of these have a namespace in the path? If the above is correct/intended, then a change like the following would be clearer for new users:
The text was updated successfully, but these errors were encountered: