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

Image versions for ml-pipeline-* pods remain in the older version after the upgrade to 1.8 #576

Open
eleblebici opened this issue Oct 11, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@eleblebici
Copy link

Bug Description

According to the version matrix here KFP backend version for Kubeflow 1.8 is 2.0.3. After the upgrade to CK 1.8, for the existing users/namespaces, ml-pipeline-* pods are still running with the older version which is 2.0.0-alpha.7 for CK 1.7.

To Reproduce

  1. deploy CK 1.7
  2. Create a user namespace
  3. Upgrade CK to 1.8

Environment

Charmed Kubeflow 1.7 and 1.8
Tested with microk8s 1.30

Relevant Log Output

microk8s kubectl describe pod ml-pipeline-visualizationserver-955b54775-fgr8f -n admin

...
Containers:
 ml-pipeline-visualizationserver:
  Container ID:  containerd://f6d0ce02ee312bbb6741e4cf1949e08a7dc2aabb87de54c24bcfd5ae36374325
  Image:     gcr.io/ml-pipeline/visualization-server:2.0.3
  Image ID:    gcr.io/ml-pipeline/visualization-server@sha256:33028a61d49d37fb22a43362cd376c45062084e453094d784017cd9186057699
...

Additional Context

No response

@eleblebici eleblebici added the bug Something isn't working label Oct 11, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6427.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant