Kuadrant / Kuadrant/testsuite-pipelines
Add task for OCP cluster provisioning in AWS
- Dominant language
- Shell
- Stars
- 0
- Forks
- 10
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 12
Description
**Summary**
This task should provision a new clean OCP cluster backed by AWS cloud provider. The way of doing this I am aware of is to use `openshift-install` cli tool. The end goal is to have a pipeline capable of creating cluster, installing Kuadrant, running tests, cleaning up. So do also an OCP cleanup task as part of this.
**Documentation**
https://docs.openshift.com/container-platform/4.16/installing/installing_aws/preparing-to-install-on-aws.html
**Parent Epic**
https://github.com/Kuadrant/testsuite-pipelines/issues/57
**Example**
`openshift-install create cluster --dir=my-cluster-config`
`openshift-install destroy cluster --dir=my-cluster-config`
The `my-cluster-config` directory should contain `install-config.yaml` file containing cluster specifications, example:
```
$ cat install-config.yaml
apiVersion: v1
baseDomain: csqeperf.link
compute:
- architecture: amd64
hyperthreading: Enabled
name: worker
platform:
aws:
type: m5.xlarge
zones:
- us-east-1a
replicas: 1
controlPlane:
architecture: amd64
hyperthreading: Enabled
name: master
platform:
aws:
type: m5.xlarge
zones:
- us-east-1a
replicas: 1
metadata:
creationTimestamp: null
name: trepel01
networking:
clusterNetwork:
- cidr: 10.128.0.0/14
hostPrefix: 23
machineNetwork:
- cidr: 10.0.0.0/16
networkType: OVNKubernetes
serviceNetwork:
- 172.30.0.0/16
platform:
aws:
region: us-east-1
userTags:
adminContact: trepel01
propagateUserTags: true
publish: External
sshKey: xxx
pullSecret: xxx
```
Contributor guide
Research direction
Start with the linked OpenShift AWS installation documentation and the issue's openshift-install examples. Define the pipeline steps around cluster creation and destruction using an install-config.yaml with the required AWS specifications, then include Kuadrant installation and tests. Done means the pipeline provisions a clean OCP cluster, runs the tests, and reliably cleans it up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell, yaml
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100