-
Notifications
You must be signed in to change notification settings - Fork 780
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
Create a V2 version of "Manipulate Kubernetes Resources as Part of a Pipeline" #3752
Comments
/area pipelines |
Is it possible to create a resource from yaml in the Kubeflowv2 version ? I checked the links but I am not able to understand how to achieve below code in KFPV2. Thank you in advance.
|
@Mohit-Verma-1688 you can ask that in our Slack. |
@thesuperzapper, it seems like we already have a v2 page for this. |
@hbelmiro I am sorry but I am not able to find an example to load a k8s yaml file. I am very new to Kubeflow and still trying to understand. My end goal is to use seldon deployment step in the pipeline and deploy the seldon crd yaml from KFP pipeline as mentioned in below example for v1. |
@Mohit-Verma-1688 This is not the right place to ask and discussing this here pollutes this issue. |
@Mohit-Verma-1688 Just to let you aware, we don't have ResourceOp support in KFPv2 and honestly I have no idea if this is still a highly demanding feature given that it's possible to create components in KFPv2 just like we did for KServe. Usually we measure the feature demand with a 👍 in the issue description, but since this is for documentation I recommend that you open an issue in kubeflow/pipelines and ask for users to 👍 the issue. |
Its quite different in V2 as it uses the
kfp[kubernetes]
library:I also note that there seem to be a few significant features missing (namely the ability to manipulate arbitrary resources, like the old v1
ResourceOp
):We could suggest people use a Python component with the
kubernetes
python library, but that should be a decision for the @kubeflow/pipelines leads.Originally posted by @thesuperzapper in #3750 (comment)
The text was updated successfully, but these errors were encountered: