-
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
[feature/idea] Integrate kubernetes's models into kfp-kubernetes #9768
Comments
Is this already being worked or is it up for grabs? What is contribution guideline and workflow in case I volunteer to implement the |
it is shocking that v2 pipelines would be released without this feature! |
The above list of missing functionality can be extended by:
|
Added them to the list! |
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. |
Commenting as this issue is still relevant |
/lifecycle frozen I'm trying to get the last issue PR and merge asap. The original contributor cannot keep contributing with it. |
Thanks for contributing with this, @cjidboon94 ! Did you see #9913? It is different from your implementation. Just wanted to check if we're not missing anything. |
Feature Area
/area backend
/area sdk
What feature would you like to see?
kfp-kubernetes
is a library that aims to extend kfp v2 with kubernetes functionality. Currently thekfp-kubernetes
package is still missing some key features imo:UserContainer
for v2? Is it deprecated completely? #9679 and Unable to run sidecar with kubeflow #9700Some of the implemented features of
kfp-kubernetes
are currently limited. For example, only secrets can be loaded as env vars/volumes while this could also be from a Config Map, a resource's field or an object's field: (via V1EnvVarSource/V1Volume respectively ) . Integration with thekubernetes
package (as was the case with KFP v1) could facillitate this. The protos thatkfp-kubernetes
requires could be generated based on the OpenAPI spec. The methods in go/python for manipulating the objects would still need to be implemented. I believe integrating the models from thekubernetes
python client package is a natural way for thekfp-kubernetes
to grow in functionality and ability.What is the use case or pain point?
Is there a workaround currently?
N/A
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: