We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We'll need to make sure we have created the corresponding tracks for all components used currently in our bundle https://github.com/canonical/bundle-kubeflow/blob/main/releases/latest/edge/bundle.yaml
This will need to happen after we've first merged
kfp-operators
minio-service
metadata-envoy
envoy
In order for us to update the bundle for the 1.8 release, and have automations just for 1.8
The text was updated successfully, but these errors were encountered:
x.x/edge
x.x/stable
Closing since all branches were cut
Sorry, something went wrong.
No branches or pull requests
What needs to get done
We'll need to make sure we have created the corresponding tracks for all components used currently in our bundle
https://github.com/canonical/bundle-kubeflow/blob/main/releases/latest/edge/bundle.yaml
This will need to happen after we've first merged
kfp-operators
upgrades from 2.0.0-alpha.7 -> 2.0.3 for CKF 1.8 release kfp-operators#362minio-service
to kfp api to patch upstream kfp bug kfp-operators#387metadata-envoy
instead ofenvoy
envoy-operator#66Why it needs to get done
In order for us to update the bundle for the 1.8 release, and have automations just for 1.8
The text was updated successfully, but these errors were encountered: