-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Pipeline deploy component does not support local model #726
Comments
Created a PR for this, the enhancement will be useful for #721 . Thanks. |
@jinchihe thanks! @gaoning777 please take a look at the PR |
Merged |
Thanks @gaoning777 |
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
magdalenakuhn17
pushed a commit
to magdalenakuhn17/pipelines
that referenced
this issue
Oct 22, 2023
* set port 80 for inference virtualservice destination. * add manager_auth_proxy_patch.yaml in development overlay as we need to pull kube-rbac-proxy image from an internal docker hub
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While I executed kubeflow Pipeline E2E TFX sample on local cluster, I found the TF-Serving cannot be started normally, checked details, that's caused by Pipeline deploy component does not support local model, so that the trained mode cannot be found after deployment pod started.
In the kubeflow section Serve a local model using Tensorflow Serving, kubeflow support nfs pvc mode for trained mode storage, pipeline should also support that.
The text was updated successfully, but these errors were encountered: