search

canonical / kubeflow-rocks

Rocks for Kubeflow components
Apache License 2.0
0 stars 11 forks source link

Update `kubeflow-central-dashboard` ROCK #91

Closed misohu closed 5 months ago

misohu commented 6 months ago

Context

Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current ROCK version against the one in the repository and adding the missing bits.

What needs to get done

  1. Clone the upstream's kubeflow repository.
  2. Go to desired Dockerfile (first line in rockcraft.yaml should specify the full path).
  3. Checkout to the branch or tag of the target version.
  4. Checkout to the branch or tag of the version of the current ROCK.
  5. Compare both files to spot the differences.

Definition of Done

  1. New ROCK is ready.
  2. Tests are passing.
  3. ROCK is published under charmedkubeflow Dockerhub account.
syncronize-issues-to-jira[bot] commented 6 months ago

Thank you for reporting us your feedback!

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

This message was autogenerated