Using Kubeflow PodDefault #1249
Unanswered
sidineycrescencio
asked this question in
Q&A
Replies: 1 comment
-
Hi @sidineycrescencio , your workaround is probably a good one for the foreseeable future. To get this working, we would need to plumb the labels all the way down to the container/k8s api from the pipeline UI, but we don't have anything in the roadmap for this level of granularity in node configuration yet. We are working on a new version of the pipeline architecture and that may make this easier in the future. We welcome any contributions you may want to make to help with these changes ! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I've created a PodDefault manifest on Kubeflow, to automatically mount a gcp credential, the problem when using Elyra is that the pods submitted via the pipeline do not have the proper labelling, therefore the secret is only mounted to the notebook server.
To get around this I can create another PodDefault using one of the labels automatically created such as "pipelines.kubeflow.org/cache_enabled=true" , but wouldn't be the most beautiful solution, and requires 2 PodDefault configs.
I wonder if there's a better way to get this working ?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions