Chain: ipi-gcp-pre-sharednetwork

The IPI setup step contains all steps that provision an OpenShift cluster in a shared network configuration on GCP.

Steps

Name Description
ipi-conf-gcp-sharednetwork This step configures an install-config.yaml file to depoloy to the GCP CI project. An existing install-config.yaml file should already exist in the shared directory. The file is modified to configure the cluster to run in the GCP CI project. The resulting file remains in the shared directory for future consumption.
ipi-install The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.

Dependencies

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

Environment

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

Variable Name Variable Content Consumed By Steps
COMPUTE_NODE_TYPE The instance type to use for compute nodes (e.g. GCP https://cloud.google.com/compute/docs/machine-types). We use a 4 core worker to match the median configuration of the fleet. (default: n1-standard-4) ipi-conf-gcp
CONTROL_PLANE_REPLICAS The number of control plane nodes to create for the cluster. This variable should only be supplied in consultation with the etcd team. The etcd operator has to explicitly support the specified number of control plane nodes and values not documented below will result in unhealthy and/or unsupportable clusters. Valid values include: * "" (default) - 3 control plane nodes. The standard for stand-alone clusters. * "1" - Supportable for single-node OpenShift (SNO). * "5" - Supportable only for select customers. (default: 3) ipi-conf-gcp
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
RT_ENABLED This flag forces the installation of real-time kernel to worker nodes. (default: false) ipi-conf-gcp
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-gcp

Step Graph

Webreg Chain "ipi-gcp-pre-sharednetwork" cluster_0 ipi-conf-gcp-sharednetwork cluster_1 ipi-install 0 ipi-conf 1 ipi-conf-gcp 0->1 2 ipi-conf-gcp-sharednetwork 1->2 3 ipi-install-monitoringpvc 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:

https://github.com/openshift/release/blob/master/ci-operator/step-registry/ipi/gcp/pre/sharednetwork/ipi-gcp-pre-sharednetwork-chain.yaml

Owners:

Approvers:

Source code for this page located on GitHub