Repo for deploying OCP to AWS

Note	fork or clone repo so that you can use Your own GitHub Secrets and worklflow.

Content

• Workflow

• Important

• TODO

Workflow

To deploy OCP4.x

1. Update variables in the install-config.yaml file

   1. baseDomain is the top level route53 domain

   2. metadata.Name is cluster name

   3. region might need to be updated

2. Ensure GitHub Secrets are created and up-to-date

   1. CLUSTER_ADMIN is the cluster admin username

   2. ADMIN_PASS is cluster admin password

   3. DEV_PASS is the password for andrew the developer

   4. PULL_SECRET is the required Red Hat creds for their repositories

   5. AWS_ACCESS_KEY_ID is the AWS Access Key

   6. AWS_SECRET_ACCESS_KEY is the AWS Secret Access key

3. Create PR to merge deploy.md to main after adding name and date to list

Note	You can now check the Actions to watch/check the status of the deployment. Also, the latest stable version of OpenShift 4 will be deployed. This can be updated or changed in the workflow deploy file.

Actions

Upon successful merge to main of deploy.md file, the workflow will automatically kick off.

1. Perform AWS IPI

2. Creates an Artifact for Destroy

   1. You can download artifact if needed from GitHub Actions > Runs

   2. Double check your retention period for Artifacts

3. Setup HTPasswd IDP

   1. Uses CLUSTER_ADMIN and ADMIN_PASS

   2. Uses DEV_PASS for andrew the developer

4. Install GitOps Operator

   1. Sets admin password for console to ADMIN_PASS

Important

• During the deploy workflow the artifacts describing the AWS resources that are deployed are needed for the destroy workflow.

• The artifacts are uploaded for only 90 days and will need to be manually downloaded if it’s not planned to destroy the cluster within that retention period.

To destroy OCP4.x

1. Push or Merge change to destroy.md

This will kick off the destroy workflow, pulling the artifact from deploy workflow automatically and destroying the AWS resources.

TODO

• Add OCP openshift-installer version as variable

Note	GitHub IDP is disabled currently

GitHub IDP

• GitHub IDP is used in this deploy, so a GitHub organization should be created

• Add the clientSecret to GitHub Secrets as CLIENT_SECRET

• Update the GitHub Organization name and clientID in idp-oauth.yaml file