Workflow: ipi-gcp

The IPI workflow provides pre- and post- steps that provision and deprovision an OpenShift cluster with a default configuration on GCP, allowing job authors to inject their own end-to-end test logic. All modifications to this workflow should be done by modifying the `ipi-gcp-{pre,post}` chains to allow other workflows to mimic and extend this base workflow without a need to backport changes.

Pre Steps

Name Description
ipi-gcp-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on GCP.

Test Steps

No test steps configured.

Post Steps

Name Description
ipi-gcp-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on GCP, provisioned by the `ipi-gcp-pre` chain.

Dependencies

Image Exposed As Override[?] Required By Steps
release:latest OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE no ipi-install-install
RELEASE_IMAGE_LATEST no ipi-install-install

Environment

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

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
TMPDIR A pathname of a directory made available for programs that need a place to create temporary files. (default: /tmp) gather-gcp-console

Step Graph

Webreg Workflow "ipi-gcp" cluster_3 Pre cluster_2 ipi-gcp-pre cluster_0 ipi-conf-gcp cluster_1 ipi-install cluster_4 Test cluster_8 Post cluster_7 ipi-gcp-post cluster_6 ipi-deprovision cluster_5 gather 0 ipi-conf 1 ipi-conf-gcp 0->1 2 ipi-install-monitoringpvc 1->2 3 ipi-install-rbac 2->3 4 openshift-cluster-bot-rbac 3->4 5 ipi-install-install 4->5 6 ipi-install-times-collection 5->6 7 Intentionally left blank 6->7 8 gather-gcp-console 7->8 9 gather-must-gather 8->9 10 gather-extra 9->10 11 gather-audit-logs 10->11 12 ipi-deprovision-deprovision 11->12

GitHub Link:

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

Owners:

Approvers:

Source code for this page located on GitHub