Chain: ipi-aws-pre-proxy

The proxy setup step contains all steps that provision an OpenShift cluster in a shared VPC configuration on AWS behind by a single proxy instance on ec2.


Name Description
ipi-conf-aws-proxy The IPI AWS configure step generates the proxy on AWS-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-install The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.


Image Exposed As Required By Steps
release:latest OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE ipi-install-install
RELEASE_IMAGE_LATEST ipi-install-install


In addition to the default environment, the following variables are consumed through this chain

Variable Name Variable Content Consumed By Steps
BASE_DOMAIN A fully-qualified domain or subdomain name. The base domain of the cloud provider is used for setting baseDomain variable of the install configuration of the cluster. (default: ipi-conf-aws
COMPUTE_NODE_TYPE (default: m5.xlarge) ipi-conf-aws-proxy ipi-conf-aws
FIPS_ENABLED (default: false) ipi-conf
OPENSHIFT_INSTALL_EXPERIMENTAL_DUAL_STACK Using experimental Azure dual-stack support (default: false) ipi-install-install
OPENSHIFT_INSTALL_PRESERVE_BOOTSTRAP Keep bootstrap resources after install. Warning: this should only be used for debugging purposes, and poses a risk to cluster stability. ipi-install-install
SIZE_VARIANT The size of the cluster in one of our supported t-shirt values that is standard across all CI environments. The sizes are: * "" (default) - 4 vCPU, 16GB control plane nodes, default workers * "compact" - 8 vCPU, 32GB control plane nodes, no workers * "large" - 16 vCPU, 64GB+ control plane nodes, default workers, suitable for clusters up to 250 nodes * "xlarge" - 32 vCPU, 128GB+ control plane nodes, default workers, suitable for clusters up to 1000 nodes These sizes are roughly consistent across all cloud providers, but we may not be able to instantiate some sizes in some regions or accounts due to quota issues. ipi-conf-aws
ZONES_COUNT The number of Availability Zones to present in the cluster. Accepted values are 1, 2, and 3. (default: 2) ipi-conf-aws-blackholenetwork ipi-conf-aws

Step Graph

Webreg Chain "ipi-aws-pre-proxy" cluster_1 ipi-conf-aws-proxy cluster_0 ipi-conf-aws-blackholenetwork cluster_2 ipi-install 0 ipi-conf 1 ipi-conf-aws-blackholenetwork 0->1 2 ipi-conf-aws 1->2 3 ipi-conf-aws-proxy 2->3 4 ipi-install-rbac 3->4 5 openshift-cluster-bot-rbac 4->5 6 ipi-install-install 5->6 7 ipi-install-times-collection 6->7

GitHub Link:



Source code for this page located on GitHub