ODS-CI Container Image files

The files for ods-ci image container are located at build folder of ods-ci GitHub repository.

An already built ods-ci image is stored in quay. "latest" tag points to RHODS v1.24.0 release branch

ODS-CI Container Documentation

Use ods-ci container to run tests according to the instructions here (without IDP creation).

The instructions are not updated to tell user how to use the IDP (identity providers) installation feature (Doc is WIP).

How to use IDP Creation options

To use OCM CLI container, it is assumed that you are connected to the cluster already, using either an IDP (different from HTPASSWD and LDAP) or a service account, or any other way you have to connect. To do so, you can create a POD on the cluster or by using the IDP install script from your local terminal (without using the ods-ci image).

Running OCM CLI container

podman run e OC_HOST=<oc_api_including_port> -e SET_ENVIRONMENT=1 -e OCM_TOKEN=<insert_your_ocm_token> -e OCM_ENV=stage   -v $PWD/<your_results_folder>:/tmp/ods-ci/test-output:Z   -e  ROBOT_EXTRA_ARGS='-i Smoke'   -e  RUN_SCRIPT_ARGS='-skip-oclogin true --set-urls-variables true'  ods-ci:<tag>

Notes:

• You can use OCM CLI way in a pod too instead of running the podman command.
• if you want to run the IDP installation script from your local terminal, ensure to export all the needed env variable before running "bash install_idp.sh". The env variables are the same you find in the pod definition (see below messages).
• The image tag convention since 1.24 is:
• Push the image to quay.io with the tag matching the x.y.z version of RHODS: e.g., 1.24.0
• Create the "latest" tag on quay pointing to x.y.z tag.
• At the moment, MPS team is pointing to "latest" tag. We may need to agree on timing, meaning that a new ods-ci image is generated after a RHODS version is released in prod, but MPS may use stage environment which has the latest RHODS before it is pushed to prod.