Chain: ipi-conf-aws-blackholenetwork

The IPI AWS blackholenetwork configure step generates the AWS-specific install-config.yaml contents based on the cluster profile and optional input files using subnets where the private ones do not have direct egress access.

Steps

Name Description
ipi-conf The IPI configure step generates the generic portions of the install-config.yaml file based on optional input files.
ipi-conf-aws-blackholenetwork The IPI AWS blackholenetwork configure step generates the AWS-specific install-config.yaml contents based on the cluster profile and optional input files using subnets where the private ones do not have direct egress access.
ipi-conf-aws The IPI AWS configure step generates the AWS-specific install-config.yaml contents based on the cluster profile and optional input files.

Dependencies

No step in this chain sets dependencies.[?]

Environment

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: origin-ci-int-aws.dev.rhcloud.com) ipi-conf-aws
COMPUTE_NODE_TYPE The instance type to use for compute nodes (e.g. AWS https://aws.amazon.com/ec2/instance-types/). We use a 4 core worker to match the median configuration of the fleet. (default: m5.xlarge) ipi-conf-aws
FIPS_ENABLED (default: false) ipi-conf
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-conf-aws-blackholenetwork" 0 ipi-conf 1 ipi-conf-aws-blackholenetwork 0->1 2 ipi-conf-aws 1->2

GitHub Link:

https://github.com/openshift/release/blob/master/ci-operator/step-registry/ipi/conf/aws/blackholenetwork/ipi-conf-aws-blackholenetwork-chain.yaml

Owners:

Approvers:

Source code for this page located on GitHub