canonical / metacontroller-rock

ROCK for metacontroller

metacontroller

ROCK for metacontroller

metacontroller-rock's Issues

Update rockraft file of metacontroller for CKF 1.8

What needs to get done

Update the corresponding rockcraft.yaml file to make sure the version of CKF 1.8 is built.

DoD:

• The rockcraft.yaml is updated
• There is automation that builds the image in each PR
• There is automation that pushes the image, once a PR is merged

Why it needs to get done

To make sure we have less CVEs in 1.8 than upstream, and enable us to be able to potentially create patches for package versions in the future

Update `metacontroller` ROCK

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.

metacontroller-rock: Update `push` and `pull_request` CI

Context

canonical/bundle-kubeflow#797

What needs to get done

Update on_push.yaml and pull_request.yaml according to example.

Definition of Done

Workflows are updated

Update metacontroller rock to `v3.0.0`

Context

Update the rockcraft.yaml file according to the Dockerfile to make sure the version of CKF 1.8 is built.

What needs to get done

1. bump the rock version
2. add sanity tests and tox.ini

Definition of Done

the rock with the new version is published