-
Notifications
You must be signed in to change notification settings - Fork 12
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
Upgrade to KFP 2.3.0 #579
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6539.
|
We expect this upgrade to be streamlined, as the manifests had minimal changes: # cd kubeflow/pipelines
cd manifests/kustomize
git checkout 2.2.0
kustomize build env/cert-manager/platform-agnostic-multi-user > manifests-2-2-0.yaml
git checkout 2.3.0
kustomize build env/cert-manager/platform-agnostic-multi-user > manifests-2-3-0.yaml
diff manifests-2-2-0.yaml manifests-2-3-0.yaml The above shows the following diff
|
Summary of the current state. We'll update KFP in CKF 1.9 to be
Regarding KFP logs and when upgrading from KFP
The fastest way to detect if a run is for V1 or V2 is by inspecting the UI. The images from #582 (comment) will make it more clear how V1 and V2 runs (and Pipeline definitions) are shown in the UI |
KFP 2.3 is now integrated in CKF 1.9/stable, see the announcement and upgrade instructions |
Context
This is primarily needed to resolve canonical/bundle-kubeflow#1120
We will need to upgrade KFP to 2.3.0 and introduce some configurations in the
kfp-ui
charm, to ensure logs are persisted. The reason we need 2.3.0 is to ensure we include this fix kubeflow/pipelines#11010What needs to get done
2.3/stable
#596Definition of Done
The text was updated successfully, but these errors were encountered: