-
Notifications
You must be signed in to change notification settings - Fork 831
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
Endpoint type is missing for AB-test #451
Comments
|
Seldon-core version is 0.2.3. All deployments I create aremain in "creating" state. I can see "Unexpected error occurred in scheduled task." messages printed periodically in the logs:
Then what is the generic way to determine from a SeldonSeployment what type endpoint it is using? (REST or GRPC?) |
Seldon will always provision REST and gRPC endpoints externally. |
For the issue on creating status it would be great if you could try a more recent release of seldon - 0.2.4 or 0.2.5? |
OK, in a few days I will be able to update my cluster, and then retest this. |
Have not seen this issue (stuck in creating) anymore with later versions. |
I deployed a single model, an AB-test and a MAB with the v1alpha2 jsonnet templates of Kubeflow.
Now, I want to list the endpoint types of the deployments (not for the subcomponents, but the "external endpoint" of the whole SeldonDeployment)
For single model and MAB it's there under "graph":
"graph": {
"endpoint": {
"service_host": ...
"service_port": ...
"type": "REST"
},
But for AB-test it is empty:
"graph": {
"endpoint": {},
I would expect that it should be filled in for AB-test deployments as well.
I am not sure if this originates from the .jsonnet templates used or from the CRD handler.
Also the status for all my SeldonDeployments seems to be stuck in "creating", even after the deployments have been working fine for several weeks:
"status": {
"state": "Creating"
}
Is this some known issue?
Thanks!
The text was updated successfully, but these errors were encountered: