-
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
cannot run through the example. #677
Comments
I tried your json on latest master image and this seems to work. Can you do: I get:
Note the Which version of the controller image is running? And which version of the Helm chart? |
$ helm version $ kubectl version $ docker version Server: $ cat /etc/centos-release $ docker images | grep seldon I get the result:
|
I do find no pods info related to the seldon in |
Can you get the services running in
|
something is wrong. |
It could be in another namespace - maybe default |
|
That looks ok. I see there is a big |
kubectl logs seldon-operator-controller-manager-0
|
I haven't installed any ingress gateway yet. Is that nessiccary? |
No should not be necessary. Are you running with any other specific settings for the helm chart? Can you posy how you installed it? |
I install seldon via the cmd: |
It seems like something changed the networking setting of k8s. I can't re-install after I del the seldon. some TLS handshaking step of k8s cluster-info complains:
|
it seems to work after I re-try several times. |
and re-create the service:
|
don't know why, but it just worked. however, the status stuck at "ContainerCreating"
|
great.
…On Tue, 9 Jul 2019, 10:26 NetWilliam, ***@***.***> wrote:
[image: image]
<https://user-images.githubusercontent.com/3966971/60876503-99167980-a26e-11e9-8caa-54af1630b7c2.png>
creating succeed finally!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#677?email_source=notifications&email_token=ACQS4A5LLU2BWO3YTTW55OTP6RKTFA5CNFSM4H7CELI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZPVYUI#issuecomment-509566033>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQS4AZ3BORLJOKIY76MSJLP6RKTFANCNFSM4H7CELIQ>
.
|
it works. thank you @cliveseldon
|
I am following the guidance of:
https://docs.seldon.io/projects/seldon-core/en/latest/workflow/README.html
https://medium.com/analytics-vidhya/manage-ml-deployments-like-a-boss-deploy-your-first-ab-test-with-sklearn-kubernetes-and-b10ae0819dfe
and
https://docs.seldon.io/projects/seldon-core/en/latest/reference/seldon-deployment.html#single-model
I have intalled the Seldon-Core in the local k8s cluster via helm, now run
kubectl get pods
return:then I have the file seldon-dep.yaml
Then I run
kubectl apply -f seldon-dep.yaml
.I am expecting to see some results after I type:
kubectl get seldondeployments -o jsonpath='{.status}'
but I see nothing.and
kubectl logs --tail=10 seldon-operator-controller-manager-0
return some logs like that:
the formatted stack trace is like:
error:
any suggestion?
The text was updated successfully, but these errors were encountered: