Skip to content
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

ApiVerisonv 2beta1 #428

Open
uhatikus opened this issue Jun 16, 2023 · 1 comment
Open

ApiVerisonv 2beta1 #428

uhatikus opened this issue Jun 16, 2023 · 1 comment
Assignees

Comments

@uhatikus
Copy link

Is it possible to migrate kubeflow from ApiVersion v1beta1 to v2beta1? How?

The following procedure:

export PIPELINE_VERSION="2.0.0-alpha.4"
kubectl apply -k "github.com/kubeflow/pipelines/manifests/kustomize/cluster-scoped-resources?ref=$PIPELINE_VERSION"
kubectl wait --for condition=established --timeout=60s crd/applications.app.k8s.io
kubectl apply -k "github.com/kubeflow/pipelines/manifests/kustomize/env/dev?ref=$PIPELINE_VERSION"

gives the error:

{"metadata":{"annotations":{"internal.kpt.dev/upstream-identifier":null,"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"apps/v1\"...```

Thank you for your answer!
@uhatikus uhatikus changed the title v2beta1 ApiVerisonv 2beta1 Jun 16, 2023
@Linchin Linchin removed their assignment Aug 28, 2023
@chensun
Copy link
Member

chensun commented Oct 19, 2023

@uhatikus The commands you pasted is for Kubeflow Pipelines standalone deployment (there's no other Kubeflow components). If that's what you intended, you can simply point PIPELINE_VERSION=2.0.2, which would support v2beta1 API.

If you do want full Kubeflow, the upcoming Kubeflow 1.8 release would also upgrade KFP API to v2beta1.

@chensun chensun self-assigned this Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants