Automate scheduled provisioning of ROSA cluster to run the 12 fips-assessment Operators

[madorn]

Automate scheduled provisioning of ROSA cluster to run the 12 fips-assessment Operators and push report to s3.

[mrhillsman]

• token obtained from https://console.redhat.com/openshift/token/rosa which requires an account (non-team member) rosa login --token=$ACCESS_TOKEN
• a non-team member specific aws account is needed as well
• one-liner to provision
• ensure cluster is up and settled
• ensure login information for the cluster is available
• once the assessments are done deprovision

[mrhillsman]

one-liner to provision

rosa create cluster --version 4.13.9 --cluster-name opcap-ansible --operator-roles-prefix opcap-ansible-0000 --fips --compute-machine-type m5.2xlarge --replicas 3 --cluster-admin-user opcap --cluster-admin-password SomeRanPassAtLeast14Chars --mint-mode

[madorn]

Prerequisite for this issue: opdev/fips-assessments#61.

We can determine workflow for Private Automation Hub before automating cluster provisioning.

[mrhillsman]

Check state of the cluster during install

rosa describe cluster -c opcap-ansible -o json|jq -r .status.state

returns "ready" when ready

Get the api endpoint for oc command

rosa describe cluster -c opcap-ansible -o json|jq -r .api.url

returns string "https://...:6443"

[mrhillsman]

Access the cluster creating a kubeconfig file at ~/.kube/config by default

oc login --insecure-skip-tls-verify=true -u opcap -p SomeRanPassAtLeast14Chars https://...:6334

rosa delete cluster -c opcap-ansible