The module will have quite a bit of edge case scenarios on how to update the KF cluster, depending on different states of the PMR. To ensure the common logic will be robust we need to ensure we have integration tests that capture a lot of the functionalities and edge case scenarios
Some of the critical functionalities we'll need to cover include:
Creating new Profiles, that are defined in PMR and don't exist in the cluster
Cleanup existing Profiles, if they are not defined in the PMR
Create RoleBindings for a contributor in a Profile, defined in the PMR
Remove a RoleBinding for a contributor in a Profile, if the contributor is not defined in the PMR
For the above we'll also need microK8s and Profile charm deployed. Also we'll need some helpers for cleaning up the Profiles between the tests.
What needs to get done
Fully flesh out which tests we want to have
Write code for cleaning up the profiles between test executions
Create a GH action that will spin up MicroK8s, the Profiles charm and run the integration tests
Definition of Done
There is a GH action that runs the integration tests
Context
This is a follow-up of https://github.com/canonical/bundle-kubeflow/issues/1144
The module will have quite a bit of edge case scenarios on how to update the KF cluster, depending on different states of the PMR. To ensure the common logic will be robust we need to ensure we have integration tests that capture a lot of the functionalities and edge case scenarios
Some of the critical functionalities we'll need to cover include:
For the above we'll also need microK8s and Profile charm deployed. Also we'll need some helpers for cleaning up the Profiles between the tests.
What needs to get done
Definition of Done