Workflow: openshift-e2e-gcp-upi

This workflow executes the common end-to-end test suite on GCP with a UPI cluster configuration.

Pre Steps

Name Description
upi-gcp-pre This chain contains all of the steps to provision an OpenShift cluster using the GCP UPI workflow.

Test Steps

Name Description
openshift-e2e-test The Openshift E2E step executes the common end-to-end test suite.

Post Steps

Name Description
upi-gcp-post This chain deprovisions all the components created by the upi-gcp-pre chain.

Dependencies

Image Exposed As Override[?] Required By Steps
release:latest OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE no openshift-e2e-test

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
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
TEST_ARGS Additional arguments to be passed to 'openshift-test' openshift-e2e-test
TEST_CSI_DRIVER_MANIFEST Name of the CSI driver manifest file to use. Used by the `openshift-tests` program as TEST_CSI_DRIVER_FILES env. var., see its documentation for details. The file must be present in ${SHARED_DIR}. openshift-e2e-test
TEST_INSTALL_CSI_DRIVERS The CSI driver(s) to use. Used by the `openshift-tests` program, see its documentation for details. openshift-e2e-test
TEST_REQUIRES_SSH If the test suite requires SSH access, setting this variable will install a bastion and configure the Kube e2e test infrastructure to use the bastion. Otherwise, tests that require SSH will fail because OpenShift does not expose SSH to nodes by default. openshift-e2e-test
TEST_SKIPS Regular expression (POSIX basic regular expression) of tests to skip. It is suggested to test the regex to make sure that it matches with the available tests. Tests can be listed by using 'openshift-tests run --dry-run (...)'. Sometimes, the tests that are printed in Prow won't exactly match the list returned by openshift-tests. openshift-e2e-test
TEST_SUITE The test suite to run. Use 'openshift-test run --help' to list available suites. (default: openshift/conformance/parallel) openshift-e2e-test
TEST_TYPE The type of test to perform. * 'suite' - Run the test suite defined by TEST_SUITE. By default this executes the OpenShift parallel conformance suite. All product components must run the default suite on pull requests prior to merge. * 'suite-conformance' - Runs the test suite defined by TEST_SUITE, then runs the product conformance suite to verify the cluster is still functional. This is typically used for testing disruption from one suite, then confirming that the disruption did not degrade the product. * 'upgrade' - Perform an upgrade to the image defined by OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE. The TEST_UPGRADE_OPTIONS flag may be optionally set. All product components must run the default upgrade test (verify an upgrade completes) on pull requests prior to merge. * 'upgrade-conformance' - Performs the 'upgrade' test and then executes the full conformance suite after upgrade completes. Does not honor TEST_SUITE but will respect TEST_UPGRADE_OPTIONS. All product releases must pass the conformance suite after an upgrade completes or have explicit logic in their test to tolerate behavior after upgrade. * 'upgrade-paused' - Perform an upgrade to the images defined by OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE with paused worker pool. (default: suite) openshift-e2e-test
TEST_UPGRADE_OPTIONS Options controlling how an upgrade is performed. See `openshift-test run-upgrade --help` for more details. openshift-e2e-test
TEST_UPGRADE_SUITE The test suite to run in upgrade tests. Use 'openshift-test run --help' to list available suites. (default: all) openshift-e2e-test

Step Graph

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

GitHub Link:

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

Owners:

Approvers:

Source code for this page located on GitHub