Pin integration tests deployed dependencies of repos [31-39]

[DnPlas]

Context

All the charms that get deployed as dependencies in integration tests must be pinned to their corresponding 1.8 stable channels in the gh:track/ branches. For instance, istio-operators deploy kubeflow-volumes in their integration tests, we must ensure that the last supported stable version of kubeflow-volumes get deployed alongside the last supported stable istio-operators.

• The resulting PR should be something like tests: point all the integration charm deps to their 1.8 versions istio-operators#405

Please follow these standards:

For variable naming:

ISTIO_CHANNEL = "1.17/stable"
ISTIO_PILOT = "istio-pilot"
ISTIO_PILOT_TRUST = True
ISTIO_GATEWAY = "istio-gateway"
ISTIO_GATEWAY_APP_NAME = "istio-ingressgateway"
ISTIO_GATEWAY_TRUST = True

For pinning COS charms:

In track/<version> pin the most stable version 1.0/stable and in main please pin the latest/stable version.

You could add a constants.py file to list all the variables and their values and import constants as a module from . import constants so you can use it in your code as constants.SOME_VAR_NAME.

• While some of the integration tests may pass, the correct way of running integration tests to keep repeatable runs is by testing always with the same versions.

• Related issue CKF 1.9: Pin the charm dependencies in the integration tests of the track/<version> branches #857

• Part of Bump juju 3.1 -> 3.5 #859

What needs to get done

For gh:track/<version> (for CKF 1.8 corresponding versions)

1. Get charms 31-39 from the bundle.yaml file.
2. Go into each charm repo and for all the test.py files where a charm is deployed, pin the channel to the version defined in the bundle definition (file from step 1).
3. Submit a PR with your changes.

For gh:main make sure all charms that get deployed in integration tests point to latest/stable unless it is recommended otherwise (e.g. mysql-k8s).

Definition of Done

All integration tests run with specific versions of charms that correspond to either CKF 1.8 or latest/stable (or recommended version)

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

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

This message was autogenerated

[ca-scribner]

so its clear, the charms being actioned here are:

• mlmd (no dependencies)
• pin integration test dependencies, refactor constants in tests minio-operator#165
• pin integration test dependencies, refactor constants in tests for track/ckf-1.8 oidc-gatekeeper-operator#145
• pin integration test dependencies, refactor constants in tests for main oidc-gatekeeper-operator#146
• pin integration test dependencies for track/1.8 pvcviewer-operator#34 (track/1.8)
• pin istio integration test dependencies in main to latest/edge pvcviewer-operator#35 (main)
• pin integration test dependencies for track/1.17 seldon-core-operator#251
• pin integration test dependencies, refactor constants in tests for track/1.8 kubeflow-tensorboards-operator#106 (tensorboard-controller and tensorboards-web-app)
• pin integration test dependencies, refactor constants in tests in track/1.7 training-operator#155

[ca-scribner]

Closed because all related PRs have merged