-
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
Seldon controller pod crashes on deploy when no internet connection available #1374
Comments
Seems it could be related to #1361 - it should be a cluster local IP address so I'm not sure why its happening. It looks like the 10.43.x.x address is broken when you close off the internet. How are you "disconneting the internet"? |
I have a single node cluster running on a laptop with K3s. I'm just disconnecting from the wireless access point... |
I'm not too familiar with K3s but it seems that it may need some extra config when there is no internet gateway set. @zjorgensenbits have you checked the following issue k3s-io/k3s#1103? |
No, I hadn't seen that issue -- thanks for the reference. I'll try that workaround in a bit and report back on what happens. |
Closing - please reopen if an issue |
I'm running v1.0 of Seldon and I've noticed that if I disconnect internet access and then try to apply a SeldonDeployment with Kubectl, the seldon-controller-manager enters a CrashLoopBackoff state and I get the following error:
Internal error occurred: failed calling webhook "mseldondeployment.kb.io": Post https://seldon-webhook-service.seldon.svc:443/mutate-machinelearning-seldon-io-v1alpha2-seldondeployment?timeout=30s: dial tcp 10.43.115.4:443: connect: network is unreachable
If I then reconnect internet access and kill the seldon-controller-manager pod, it respawns fine and I'm able to deploy again without problems.
I'm interested to know what causes this to happen and whether it is resolvable, as I will need to be able to deploy models without an internet connection.
This could be related to issue #1361, but I'm not sure.
The text was updated successfully, but these errors were encountered: