-
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
initContainer tfserving-model-initializer is not able to pull model from s3 #3330
Comments
/cc @hemantha-kumara |
Have you tried with the latest seldon core that uses rclone? |
The root of the problem is that init-containers DO NOT work well withIstio sidecar proxy. Is there any possibility in Seldon to have the models fetched remotely outside of init-containers. If such an option is available it can be used. |
It seems there's a suggested fix that could be used through istio specific annotations @nrchakradhar have you tried this? https://stackoverflow.com/questions/64356701/allow-requests-to-kubernetes-api-from-an-init-container-with-istio-cni-plugin |
@axsaucedo Thanks for the reference. The exclusion option has not been an encouraging solution. If model fetching can be made outside of the init-container, it will be useful. We are using without Istio in certain configurations. |
We will need more information about the Istio configuration that is causing the issue, just presence of sidecars is not enough. I have just deployed
in namespace with sidecars injections enabled:
without any issues. I observed that rclone init container executed before Seldon Core: 1.11.2 |
Closing. Please reopen if still an issue |
The workaround only works, if the model source is outside the service mesh, e.g. google storage. I am running a minio instance inside the service mesh and would like to pull models from there. |
Describe the bug
When SeldonDeployment is created with istio siddecar injection enabled with mtls strict mode
initContainer tfserving-model-initializer is not able to pull model from s3
There is a known issue in istio side that initContainer will not be able to do outside calls
istio/istio#11130
To reproduce
Expected behaviour
tfserving-model-initializer initContainer should be able to fetch the model from s3 uri
Environment
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.5", GitCommit:"e338cf2c6d297aa603b50ad3a301f761b4173aa6", GitTreeState:"clean", BuildDate:"2020-12-09T11:18:51Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.5", GitCommit:"e338cf2c6d297aa603b50ad3a301f761b4173aa6", GitTreeState:"clean", BuildDate:"2020-12-09T11:10:32Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
kubectl get --namespace seldon-system deploy seldon-controller-manager -o yaml | grep seldonio
] docker.io/seldonio/seldon-core-operator:1.6.0Model Details
kubectl get seldondeployment -n <yourmodelnamespace> <seldondepname> -o yaml | grep image:
where<yourmodelnamespace>
]seldonio/tfserving-proxy:1.6.0
tensorflow/serving:2.1.0
The text was updated successfully, but these errors were encountered: