-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
KFP should support containerd runtime on Kube #678
Comments
Could you give more context on why it's needed? We rely on argo to copy the artifact files. However, only docker executor currently supports file operations in argo (https://github.com/argoproj/argo/tree/master/workflow/executor). There is an argo FR to get rid of docker cp and it seems that argo team had a plan but still WIP. |
@hongye-sun we are moving towards containerd in IBM Cloud IKS, and hence this becomes key |
Hi folks - coming back to this. Given we have phased out support for docker in IBM Kubernetes service, this is becoming a blocker. Anyway to take this forward jointly with Argo? |
Thanks for filing the issue with Argo. Would you be able to drive support for containerd with both Argo and then KFP? Let me know if some help is needed. |
Thanks @vicaire. Definitely chasing it - there is a PR with Argo which are trying to make it work within our context, and then will be going back with what still remains opens. |
Hey @animeshsingh, with new process namespace sharing (PNS) I got argo to run with containerd on k3s, no docker involved. You can use it by setting a property in the config map as described in #901 here Does this solve your problem? |
For those who have the same issue, add or change |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
Does this work without needing to modify Argo? |
…ployments. (kubeflow#678) * Update get_kf_testing_cluster to work with blueprints * With GCP blueprints we won't have deployments so we need to list clusters by name and find cluster with matching regex. * Create an ACM repo for kf-ci-v1 cluster and hydrate it with the appropriate manifests for the auto-deploy and tektoncd namespaces. * kubeflow/testing#677 is tracking using ACM with the cluster kf-ci-v1 * Note this PR is only using ACM to sync tekton resources; we still need to sync the rest of the auto-deployment infrastructure like the reconciler and webserver. * Remove ACM cluster selector; ACM complains because it isn't actually being applied. * Override notebook-test-task.yaml with nb-test-task.yaml. The latter should include the latest changes from Gabriel's PR. * When deploying the blueprint we need to do `kpt cfg set email` to set the email for the default profile. Without this change the deployment won't include the namespace we need to run the tests in GoogleCloudPlatform/kubeflow-distribution#42 is tracking CI for the blueprints.
* Add documentation for custom sample * Add TARGET env var * Add requirements.txt and update README * kfservingsdk example * Add expected output * Update model name
KubeFlow pipeline currently only works on Docker runtime since the pipeline output artifacts are copied with "docker cp" command. We need support for containerd runtime
The text was updated successfully, but these errors were encountered: