Workflows

Workflows are the highest level registry components, defining a test from start to finish.

Name and Description Steps
Name: baremetalds-assisted

Description:
This workflow executes the common end-to-end test suite on a cluster provisioned by running assisted-installer on a packet server.

Pre: Test: Post:
Name: baremetalds-assisted-install

Description:
This workflow installs an OCP cluster by running assisted-installer on a packet server.

Pre: Test: Post:
Name: baremetalds-assisted-operator-ztp

Description:
Using hub-cluster with Assisted Service operator to deploy extra workers as spoke clusters. Installation will be following ZTP flow (Zero Touch Provisioning), meaning no explicit provisioning actions will be made outside of the system.

Pre: Post:
Name: baremetalds-assisted-operator-ztp-upgrade

Description:
Using hub-cluster with Assisted Service operator to deploy extra workers as spoke clusters. Installation will be following ZTP flow (Zero Touch Provisioning), meaning no explicit provisioning actions will be made outside of the system. First, AI operator with version ocm-2.3 is installed and a spoke SNO cluster is deployed. The subscription is updated to upgrade the AI operator from ocm-2.3 to the latest version to upgrade the AI operator. Once the operator is upgraded, a new spoke SNO cluster is installed.

Pre: Post:
Name: baremetalds-e2e

Description:
This workflow executes the common end-to-end test suite on a cluster provisioned by running dev-scripts on a packet server.

Pre: Test: Post:
Name: baremetalds-e2e-ovn-ipsec

Description:
This workflow executes the common end-to-end test suite on a cluster provisioned by running dev-scripts on a packet server with IPsec enabled.

Pre: Test: Post:
Name: baremetalds-e2e-serial-ipv4

Description:
This workflow executes the ipv4 end-to-end serial test suite on a cluster provisioned by running dev-scripts on a packet server.

Pre: Test: Post:
Name: baremetalds-e2e-upgrade

Description:
This workflow executes the common end-to-end upgrade test suite on a cluster provisioned by running dev-scripts on a packet server.

Pre: Test: Post:
Name: baremetalds-e2e-virtualmedia

Description:
This workflow executes the common end-to-end test suite on a virtualmedia based deployment by running dev-scripts on a packet server.

Pre: Test: Post:
Name: baremetalds-metallb-e2e

Description:
This workflow executes the metallb end-to-end test suite on a cluster provisioned by running dev-scripts on a packet server.

Pre: Test: Post:
Name: baremetalds-sno

Description:
This workflow executes single-node installation using live CD.

Pre: Test: Post:
Name: code-ready-crc-e2e

Description:
The crc E2E workflow executes the common end-to-end test suite on CRC with a GCP nested cluster configuration.

Pre: Test: Post:
Name: code-ready-crc-integration

Description:
The crc integration workflow executes the common end-to-end test suite on CRC with a GCP nested cluster configuration.

Pre: Test: Post:
Name: code-ready-snc-e2e

Description:
The snc E2E workflow executes the common end-to-end test suite for snc with a GCP nested cluster configuration.

Pre: Test: Post:
Name: cucushift-aws-ipi

Description:
The workflow executes cucushift e2e tests

Pre: Test: Post:
Name: generic-claim

Description:
This workflows perform shared pre/post actions on clusters obtained from preinstalled pools (https://docs.ci.openshift.org/docs/architecture/ci-operator/#testing-with-a-cluster-from-a-cluster-pool). The intent of this workflow is to mimic the `ipi-$PLATFORM` workflow behavior, just without the installation/deprovision steps.

Pre: Post:
Name: hypershift-launch-aws

Description:
The HyperShift launch workflow executes tests against a new ephemeral HyperShift cluster. Administrative access to the control plane is provided via the `KUBECONFIG` environment variable. Note that tests will execute once the control plane is ready, regardless of whether nodes have been requested, have joined, or are available. The control plane is hosted on a dedicated standalone OCP cluster running HyperShift in the `osd-hypershift` AWS account and is destroyed after tests complete. The HyperShift launch capability is currently supported by the HyperShift team. For now, please direct all questions and comments to: - Alberto Lamela (agarcial@redhat.com) - Seth Jennings (sjenning@redhat.com) - Dan Mace (dmace@redhat.com) - Cesar Wong (cewong@redhat.com) Learn more about HyperShift here: https://github.com/openshift/hypershift Track HyperShift's development here: https://issues.redhat.com/projects/HOSTEDCP

Pre: Post:
Name: identitatem-ci-image-mirror

Description:
This workflow mirrors an image from the CI Registry to a given image ref.

Pre:
Name: identitatem-ci-rbac

Description:
This workflow adds the necessary privileges to the Prow job's namespace so that images can be accessed outside the Prow clusters.

Pre:
Name: ipi-aws

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

Pre: Post:
Name: ipi-aws-ovn

Description:
IPI workflow that provision and deprovision an OpenShift cluster with OVNKube network on AWS.

Pre: Post:
Name: ipi-aws-ovn-hybrid

Description:
OpenShift cluster configured with Hybrid OVN network

Pre: Post:
Name: ipi-aws-ovn-hybrid-custom-vxlan-port

Description:
OpenShift cluster configured with Hybrid OVN network with custom vxlan port set to 9789

Pre: Post:
Name: ipi-azure

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

Pre: Post:
Name: ipi-azure-arcconformance

Description:
The Azure Arc conformance worflow runs the Arc Enabled Kubernetes Validation Program[1] suite on top of an Azure IPI cluster and publishes the results in the artifacts directory. [1] https://github.com/Azure/azure-arc-validation.

Pre: Test: Post:
Name: ipi-azure-ovn-hybrid

Description:
OpenShift Azure cluster configured with Hybrid OVN networking

Pre: Post:
Name: ipi-azurestack

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

Pre: Post:
Name: ipi-gcp

Description:
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: Post:
Name: ipi-kubevirt

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

Pre: Post:
Name: ipi-libvirt

Description:
The IPI workflow provides pre- and post- steps that provision and deprovision an OpenShift cluster with a default configuration on libvirt, allowing job authors to inject their own end-to-end test logic.

Pre: Post:
Name: ipi-openstack

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

Pre: Post:
Name: ipi-vsphere-ovn-hybrid-custom-vxlan-port

Description:
OpenShift cluster configured with Hybrid OVN network on vSphere

Pre: Post:
Name: ocm-ci-fastforward

Description:
This workflow fast forwards a source branch to a destination branch in a GitHub repo.

Test:
Name: ocm-ci-image-mirror

Description:
This workflow mirrors an image from the CI Registry to a given image ref.

Pre:
Name: ocm-ci-rbac

Description:
This workflow adds the necessary privileges to the Prow job's namespace so that images can be accessed outside the Prow clusters.

Pre:
Name: ocm-e2e-clusterpool

Description:
This workflow checks out one or more clusters for use by a test and then checks the clusters back in when done.

Pre: Post:
Name: ocm-e2e-kind

Description:
This workflow creates a VM with KinD installed to run test and then destroys the VM when done.

Pre: Post:
Name: openshift-e2e-aws

Description:
The Openshift E2E AWS workflow executes the common end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-builds

Description:
The Openshift E2E AWS `builds` workflow executes the `openshift/build` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-calico

Description:
The Openshift E2E Calico workflow executes the common end-to-end test suite with the Calico network plugin with default configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-ccm

Description:
The Openshift E2E AWS workflow using CCM as a primary mean to initialize nodes and create external LoadBalancers. Executes the common end-to-end test suite on AWS to test updated cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-ccm-install

Description:
The Openshift E2E AWS CCM install workflow executes the common end-to-end test suite on AWS with a cluster configuration including CCM pods

Pre: Test: Post:
Name: openshift-e2e-aws-cgroupsv2

Description:
The Openshift E2E cgroupsv2 workflow executes the common end-to-end test suite with nodes configured to use cgroupsv2.

Pre: Test: Post:
Name: openshift-e2e-aws-cilium

Description:
The Openshift E2E Cilium workflow executes the common end-to-end test suite with the Cilium network plugin with default configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-cmd

Description:
The Openshift E2E AWS `cmd` workflow executes the `openshift/test-cmd` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-csi

Description:
The Openshift E2E AWS `csi` workflow executes the `openshift/csi` end-to-end test suite on AWS EBS CSI driver that was installed during cluster setup.

Pre: Test: Post:
Name: openshift-e2e-aws-csi-efs

Description:
The Openshift E2E AWS `csi` workflow executes the `openshift/csi` end-to-end test suite on AWS EFS CSI driver that was installed during cluster setup.

Pre: Test: Post:
Name: openshift-e2e-aws-csi-install

Description:
The Openshift E2E AWS `csi` workflow installs AWS EBS CSI driver and executes the `openshift/csi` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-csi-migration

Description:
This workflow enables CSI migration for all volume plugins and runs e2e tests (which include AWS EBS in-tree tests).

Pre: Test: Post:
Name: openshift-e2e-aws-disruption

Description:
The Openshift E2E AWS disruption workflow executes disruption test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-disruption-ovn

Description:
The Openshift E2E AWS OVN disruption workflow executes disruption test suite on AWS with the OVNKubernetes network plugin.

Pre: Test: Post:
Name: openshift-e2e-aws-hosted-loki

Description:
The Openshift E2E AWS workflow executes the common end-to-end test suite on AWS with a default cluster configuration with Loki hosted on Observatorium as log collector.

Pre: Test: Post:
Name: openshift-e2e-aws-image-ecosystem

Description:
The Openshift E2E AWS `image-ecosystem` workflow executes the `openshift/image-ecosystem` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-image-registry

Description:
The Openshift E2E AWS `image-registry` workflow executes the `openshift/image-registry` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-jenkins

Description:
The Openshift E2E AWS `jenkins` workflow executes the `openshift/jenkins` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-loki

Description:
The Openshift E2E AWS workflow executes the common end-to-end test suite on AWS with a default cluster configuration with loki as log collector.

Pre: Test: Post:
Name: openshift-e2e-aws-manual-oidc-sts

Description:
The Openshift E2E AWS workflow executes the common end-to-end test with user defined OIDC provider and IAM roles on AWS for operators.

Pre: Test: Post:
Name: openshift-e2e-aws-ovn

Description:
The Openshift E2E OVN workflow executes the common end-to-end test suite with the OVNKubernetes network plugin.

Pre: Test: Post:
Name: openshift-e2e-aws-ovn-hybrid

Description:
The Openshift E2E OVN workflow executes the common end-to-end test suite with the OVNKubernetes network plugin with a configured hybrid network.

Pre: Test: Post:
Name: openshift-e2e-aws-ovn-ipsec

Description:
The Openshift E2E OVN workflow executes the common end-to-end test suite with the OVNKubernetes network plugin with IPsec configured.

Pre: Test: Post:
Name: openshift-e2e-aws-proxy

Description:
The Openshift E2E AWS workflow executes the common end-to-end test suite on AWS with a proxy cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-sdn-multi

Description:
The Openshift E2E SDN multi workflow executes the common end-to-end test suite with the OpenShiftSDN multitenant network plugin.

Pre: Test: Post:
Name: openshift-e2e-aws-serial

Description:
The Openshift E2E AWS `serial` workflow executes the `openshift/serial` end-to-end test suite on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-sharednetwork

Description:
The Openshift E2E AWS workflow executes the common end-to-end test suite on AWS in a shared network cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-single-node

Description:
The Openshift E2E Single Node workflow executes the common end-to-end test suite with the a single node cluster.

Pre: Test: Post:
Name: openshift-e2e-aws-techpreview

Description:
The Openshift E2E AWS workflow executes the common end-to-end test suite on AWS with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-techpreview-serial

Description:
The Openshift E2E AWS `serial` workflow executes the `openshift/serial` end-to-end test suite on AWS with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-aws-workers-rhel

Description:
The OpenShift E2E AWS workflow executes the common end-to-end test suite on AWS with RHEL workers.

Pre: Test: Post:
Name: openshift-e2e-azure

Description:
The Openshift E2E Azure workflow executes the common end-to-end test suite on Azure with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-ccm

Description:
The Openshift E2E Azure workflow using CCM as a primary mean to initialize nodes. Executes the common end-to-end test suite on Azure to test updated cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-ccm-install

Description:
The Openshift E2E Azure CCM install workflow executes the common end-to-end test suite on Azure with a cluster configuration including CCM pods

Pre: Test: Post:
Name: openshift-e2e-azure-cilium

Description:
The Openshift E2E Cilium workflow executes the common end-to-end test suite with the Cilium network plugin with default configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-csi

Description:
The Openshift E2E GCP `csi` workflow executes the `openshift/csi` end-to-end test suite on Azure Disk CSI driver that was installed during cluster setup.

Pre: Test: Post:
Name: openshift-e2e-azure-csi-migration

Description:
This workflow enables CSI migration for all volume plugins and runs e2e tests (which include Azure Disk in-tree tests).

Pre: Test: Post:
Name: openshift-e2e-azure-ovn

Description:
The Openshift E2E OVN workflow executes the common end-to-end test suite with the OVNKubernetes network plugin.

Pre: Test: Post:
Name: openshift-e2e-azure-ovn-dualstack

Description:
The Openshift E2E OVN workflow executes the common end-to-end test suite in Azure with the OVNKubernetes network plugin with dualstack configured.

Pre: Test: Post:
Name: openshift-e2e-azure-resourcegroup

Description:
The Openshift E2E Azure workflow executes the common end-to-end test suite on Azure in an existing Resource Group configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-serial

Description:
The Openshift E2E Azure `serial` workflow executes the `openshift/serial` end-to-end test suite on Azure with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-sharednetwork

Description:
The Openshift E2E Azure workflow executes the common end-to-end test suite on Azure in a shared Virtual Network configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-techpreview

Description:
The Openshift E2E Azure workflow executes the common end-to-end test suite on Azure with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azure-techpreview-serial

Description:
The Openshift E2E Azure `serial` workflow executes the `openshift/serial` end-to-end test suite on Azure with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azurestack

Description:
The Openshift E2E Azure workflow executes the common end-to-end test suite on Azure with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azurestack-upi

Description:
The Openshift E2E Azure workflow executes the common end-to-end test suite on Azure with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-azurestack-upi-csi

Description:
The Openshift E2E AzureStack `csi` workflow executes the `openshift/csi` end-to-end test suite on Azure Disk CSI driver on Azure Stack.

Pre: Test: Post:
Name: openshift-e2e-gcp

Description:
The Openshift E2E GCP workflow executes the common end-to-end test suite on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-builds

Description:
The Openshift E2E GCP `builds` workflow executes the `openshift/build` end-to-end test suite on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-cilium

Description:
The Openshift E2E Cilium workflow executes the common end-to-end test suite with the Cilium network plugin with default configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-cmd

Description:
The Openshift E2E GCP `cmd` workflow executes the `openshift/test-cmd` end-to-end test suite on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-crc

Description:
The snc E2E workflow executes the common end-to-end test suite for crc for installer with a GCP nested cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-csi

Description:
The Openshift E2E GCP `csi` workflow executes the `openshift/csi` end-to-end test suite on GCP PD CSI driver that was installed during cluster setup.

Pre: Test: Post:
Name: openshift-e2e-gcp-csi-migration

Description:
This workflow enables CSI migration for all volume plugins and runs e2e tests (which include GCP PD in-tree tests).

Pre: Test: Post:
Name: openshift-e2e-gcp-disruption

Description:
The Openshift E2E GCP disruption workflow executes disruption test suite on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-disruption-ovn

Description:
The Openshift E2E GCP disruption workflow executes disruption test suite on GCP with the OVNKubernetes network plugin.

Pre: Test: Post:
Name: openshift-e2e-gcp-hosted-loki

Description:
The Openshift E2E GCP workflow executes the common end-to-end test suite on GCP with a default cluster configuration with loki as log collector hosted on Observatorium.

Pre: Test: Post:
Name: openshift-e2e-gcp-image-ecosystem

Description:
The Openshift E2E GCP `image-ecosystem` workflow executes the `openshift/image-ecosystem` end-to-end test suite on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-libvirt

Description:
The libvirt E2E workflow executes the common end-to-end test suite on openshift with a GCP nested cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-libvirt-cert-rotation

Description:
The gcp libvirt cert-rotation E2E workflow executes openshift with a GCP nested cluster and sets it 1 year ahead.

Pre: Test: Post:
Name: openshift-e2e-gcp-loki

Description:
The Openshift E2E GCP workflow executes the common end-to-end test suite on GCP with a default cluster configuration with loki as log collector.

Pre: Test: Post:
Name: openshift-e2e-gcp-ovn

Description:
The Openshift E2E OVN workflow executes the common end-to-end test suite with the OVNKubernetes network plugin.

Pre: Test: Post:
Name: openshift-e2e-gcp-realtime

Description:
The Openshift E2E GCP realtime workflow executes the common end-to-end test suite on GCP with realtime kernel workers.

Pre: Test: Post:
Name: openshift-e2e-gcp-serial

Description:
The Openshift E2E GCP `serial` workflow executes the `openshift/serial` end-to-end test suite on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-sharednetwork

Description:
The Openshift E2E GCP workflow executes the common end-to-end test suite on GCP with a shared network cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-single-node

Description:
The Openshift E2E Single Node workflow executes the common end-to-end test suite with the a single node cluster.

Pre: Test: Post:
Name: openshift-e2e-gcp-techpreview

Description:
The Openshift E2E GCP workflow executes the common end-to-end test suite on GCP with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-techpreview-serial

Description:
The Openshift E2E GCP `serial` workflow executes the `openshift/serial` end-to-end test suite on GCP with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-gcp-upi

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

Pre: Test: Post:
Name: openshift-e2e-gcp-upi-xpn

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

Pre: Test: Post:
Name: openshift-e2e-ibmz-eco-upi

Description:
IBM Z E2E wraps the Openshift E2E workflow and executes the common end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-kubevirt

Description:
The Openshift E2E KubeVirt workflow executes the common end-to-end test suite on KubeVirt with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-kubevirt-networktype

Description:
The Openshift E2E KubeVirt workflow executes the common end-to-end test suite with a dynamic networkType plugin on KubeVirt with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-libvirt

Description:
The IPI workflow provides pre- and post- steps that provision and deprovision an OpenShift cluster with a default configuration on libvirt, allowing job authors to inject their own end-to-end test logic.

Pre: Test: Post:
Name: openshift-e2e-openstack-byon

Description:
The openshift-e2e-openstack-byon workflow executes the common end-to-end test suite on OpenShift BYON installation on OpenStack.

Pre: Test: Post:
Name: openshift-e2e-openstack-ccm

Description:
The openshift-e2e-openstack-ipi workflow executes the common end-to-end test suite on OpenShift ipi intallation on OpenStack with the default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-openstack-csi-cinder

Description:
The Openshift E2E OpenStack `csi cinder` workflow installs OpenStack Cinder CSI driver and executes the `openshift/csi` end-to-end test suite on OpenStack with a default cluster configuration and a manifest to test Cinder resources.

Pre: Test: Post:
Name: openshift-e2e-openstack-csi-manila

Description:
The Openshift E2E OpenStack `csi manila` workflow installs OpenStack Manila CSI driver and executes the `openshift/csi` end-to-end test suite on OpenStack with a default cluster configuration and a manifest to test Manila resources.

Pre: Test: Post:
Name: openshift-e2e-openstack-ipi

Description:
The openshift-e2e-openstack-ipi workflow executes the common end-to-end test suite on OpenShift ipi intallation on OpenStack with the default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-openstack-proxy

Description:
The openshift-e2e-openstack-proxy workflow executes an installation of OpenShift with Proxy using a restricted BYON installation on OpenStack.

Pre: Test: Post:
Name: openshift-e2e-openstack-techpreview

Description:
The openshift-e2e-openstack-techpreview workflow executes the common end-to-end test suite on OpenShift ipi intallation on OpenStack with the TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-ovirt-clusterbot

Description:
The Openshift E2E oVirt clusterbot workflow installs an OpenShift cluster on top of oVirt and for testing and development purposes via the slack clusterbot, see openshift/ci-chat-bot

Pre: Test: Post:
Name: openshift-e2e-ovirt-conformance

Description:
The Openshift E2E oVirt e2e workflow installs OpenShift cluster on top of oVirt. Executes the `openshift/conformance/parallel` end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-ovirt-conformance-release-4.4-4.5

Description:
The Openshift E2E oVirt e2e release 4.4,4.5 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain the oVirt csi driver, therefor patch the image registry. Executes the `openshift/conformance/parallel` end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-ovirt-conformance-release-4.6-4.7

Description:
The Openshift E2E oVirt e2e release 4.6,4.7 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain affinity groups and secure connection to the oVirt engine from the installer, therefor it uses a different install config and ovirt-config. Executes the `openshift/conformance/parallel` end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-ovirt-csi

Description:
The Openshift E2E oVirt `csi` workflow installs OpenShift cluster on top of oVirt Executes the `openshift/csi` end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-ovirt-csi-release-4.6-4.7

Description:
The Openshift E2E oVirt `csi` release 4.6,4.7 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain affinity groups and secure connection to the oVirt engine from the installer, therefor it uses a different install config and ovirt-config. Executes the `openshift/csi` end-to-end test suite. Volume resizing tests are disabled, releases 4.6,4.7 doesn't support volume resizing.

Pre: Test: Post:
Name: openshift-e2e-ovirt-csi-release-4.8

Description:
The Openshift E2E oVirt `csi` workflow installs OpenShift cluster on top of oVirt Executes the `openshift/csi` end-to-end test suite. Volume resizing tests are disabled, release 4.8 doesn't support volume resizing

Pre: Test: Post:
Name: openshift-e2e-ovirt-minimal

Description:
The Openshift E2E oVirt e2e minimal workflow installs OpenShift cluster on top of oVirt Executes confotmance "Early" tests only.

Pre: Test: Post:
Name: openshift-e2e-ovirt-minimal-release-4.4-4.5

Description:
The Openshift E2E oVirt e2e minimal release 4.4,4.5 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain the oVirt csi driver, therefor patch the image registry. Executes confotmance "Early" tests only.

Pre: Test: Post:
Name: openshift-e2e-ovirt-minimal-release-4.6-4.7

Description:
The Openshift E2E oVirt e2e minimal release 4.6,4.7 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain affinity groups and secure connection to the oVirt engine from the installer, therefor it uses a different install config and ovirt-config. Executes confotmance "Early" tests only.

Pre: Test: Post:
Name: openshift-e2e-powervs-upi

Description:
Wraps the Openshift E2E workflow and executes the common end-to-end test suite running on a cluster at IBM Cloud on PowerVS.

Pre: Test: Post:
Name: openshift-e2e-vsphere

Description:
VSphere E2E wraps the Openshift E2E workflow and executes the common end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-vsphere-csi

Description:
The Openshift E2E vSphere `csi` workflow executes the `openshift/csi` end-to-end test suite on vSphere CSI driver that was installed during cluster setup.

Pre: Test: Post:
Name: openshift-e2e-vsphere-ovn

Description:
The origin E2E vsphere OVN workflow executes the common end-to-end test suite with OVNKubernetes network plugin on vsphere.

Pre: Test: Post:
Name: openshift-e2e-vsphere-serial

Description:
The Openshift E2E vSphere `serial` workflow executes the `openshift/serial` end-to-end test suite on vSphere with a default cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-vsphere-techpreview

Description:
The Openshift E2E VSphere workflow executes the common end-to-end test suite on VSphere with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-vsphere-techpreview-serial

Description:
The Openshift E2E VSphere `serial` workflow executes the `openshift/serial` end-to-end test suite on VSphere with a TechPreviewNoUpgrade cluster configuration.

Pre: Test: Post:
Name: openshift-e2e-vsphere-upi

Description:
VSphere E2E wraps the Openshift E2E workflow and executes the common end-to-end test suite.

Pre: Test: Post:
Name: openshift-e2e-vsphere-upi-serial

Description:
The Openshift E2E vSphere `serial` workflow executes the `openshift/serial` end-to-end test suite on vSphere with a default cluster configuration.

Pre: Test: Post:
Name: openshift-kubernetes-e2e-aws

Description:
The Kubernetes E2E workflow executes the parallel e2e tests built from the openshift/kubernetes fork of k8s.io/kubernetes on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-kubernetes-e2e-aws-serial

Description:
The Kubernetes E2E Serial workflow executes the serial e2e tests built from the openshift/kubernetes fork of k8s.io/kubernetes on AWS with a default cluster configuration.

Pre: Test: Post:
Name: openshift-kubernetes-e2e-gcp

Description:
The Kubernetes E2E workflow executes the parallel e2e tests built from the openshift/kubernetes fork of k8s.io/kubernetes on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-kubernetes-e2e-gcp-serial

Description:
The Kubernetes E2E Serial workflow executes the serial e2e tests built from the openshift/kubernetes fork of k8s.io/kubernetes on GCP with a default cluster configuration.

Pre: Test: Post:
Name: openshift-manifests-openstack

Description:
The OpenStack-specific manifest-generation test suite.

Pre: Test:
Name: openshift-perfscale-e2e-configmap-scale

Description:
The OpenShift E2E configmap-scale is a workload focused at stressing the API and etcd componentes by generating configmap churn

Pre: Test: Post:
Name: openshift-psap-e2e-aws-gpu

Description:
The Openshift-PSAP GPU E2E AWS workflow executes the common end-to-end test suite on AWS with a GPU node.

Pre: Test: Post:
Name: openshift-upgrade-aws

Description:
The Openshift E2E AWS workflow executes the upgrade end-to-end test suite on AWS with a default cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-aws-latestinstaller

Description:
The Openshift E2E AWS workflow executes the upgrade end-to-end test suite on AWS with a default cluster configuration and Loki as log collector, exercising an upgrade during the process. Installer from latest release is used instead. This workflow is intended to verify that changes in installer PR can be used to upgrade the cluster later on.

Pre: Test: Post:
Name: openshift-upgrade-aws-ovn

Description:
The Openshift E2E AWS OVN workflow executes the upgrade end-to-end test suite on AWS with a default cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-aws-pausedworkers

Description:
The Openshift E2E AWS workflow executes the upgrade to images in OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE with minimal worker pool distruption by pausing the worker pool until the final upgrade.

Pre: Test: Post:
Name: openshift-upgrade-aws-single-node

Description:
The Openshift E2E AWS single node workflow executes the upgrade end-to-end test suite on AWS with a default single-node cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-azure

Description:
The Openshift E2E Azure workflow executes the upgrade end-to-end test suite on Azure with a default cluster configuration and Loki as a log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-azure-ovn

Description:
The Openshift E2E Azure OVN workflow executes the upgrade end-to-end test suite on Azure with a default cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-azure-single-node

Description:
The Openshift E2E Azure single node workflow executes the upgrade end-to-end test suite on Azure with a default single-node cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-gcp

Description:
The Openshift E2E GCP workflow executes the upgrade end-to-end test suite on GCP with a default cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-gcp-latestinstaller

Description:
The Openshift E2E GCP workflow executes the upgrade end-to-end test suite on GCP with a default cluster configuration and Loki as log collector, exercising an upgrade during the process. Installer from latest release is used instead. This workflow is intended to verify that changes in installer PR can be used to upgrade the cluster later on.

Pre: Test: Post:
Name: openshift-upgrade-gcp-ovn

Description:
The Openshift E2E GCP OVN workflow executes the upgrade end-to-end test suite on GCP with a default cluster configuration and Loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-openstack-loki

Description:
The Openshift E2E openstack workflow executes the upgrade end-to-end test suite on openstack with a default cluster configuration and loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openshift-upgrade-ovirt

Description:
The Openshift E2E oVirt upgrade workflow installs OpenShift cluster on top of oVirt and executes an upgrade to the next available version.

Pre: Test: Post:
Name: openshift-upgrade-ovirt-release-4.4-4.5

Description:
The Openshift E2E oVirt upgrade release 4.4,4.5 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain the oVirt csi driver, therefor patch the image registry. Executes an upgrade to the next available version.

Pre: Test: Post:
Name: openshift-upgrade-ovirt-release-4.6-4.7

Description:
The Openshift E2E oVirt upgrade release-4.6,4.7 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain affinity groups and secure connection to the oVirt engine from the installer, therefor it uses a different install config and ovirt-config. Executes an upgrade to the next available version.

Pre: Test: Post:
Name: openshift-upgrade-vsphere

Description:
The Openshift E2E vSphere workflow executes the upgrade end-to-end test suite on vSphere with a default cluster configuration and loki as log collector, exercising an upgrade during the process.

Pre: Test: Post:
Name: openstack-provision-virtual

Description:
THIS IS A PLACEHOLDER. This workflow provisions a virtual machine where to test the OpenStack-provisioning scripts.

Test:
Name: operator-pipelines-preflight-common-claim

Description:
This workflows perform shared pre/post actions on clusters obtained from preinstalled pools (https://docs.ci.openshift.org/docs/architecture/ci-operator/#testing-with-a-cluster-from-a-cluster-pool). Claims a cluster with a default configuration on AWS and executes the Preflight tool against a provided asset. Important: Parameter values in `env` are supposed to be used only in rehearsals and serve as "testing defaults". Production jobs should always override them via `preflight-trigger`.

Pre: Test: Post:
Name: operatorhub

Description:
Installs a cluster with a default configuration on AWS, install an optional operator using the input package and channel from the OperatorHub.

Pre: Post:
Name: optional-operators-ci-aws

Description:
Installs a cluster with a default configuration on AWS and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-aws-ovn-hybrid

Description:
Installs a cluster with hybrid OVN networking on AWS and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-aws-ovn-hybrid-custom-vxlan-port

Description:
Installs a cluster with hybrid OVN networking on AWS with custom vxlan port set to 9789 and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-aws-upgrade

Description:
Installs a cluster with a default configuration on AWS and installs an specified initial version of an operator and then upgrades to the latest bundle from the built index.

Pre: Post:
Name: optional-operators-ci-azure

Description:
Installs a cluster with a default configuration on Azure and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-azure-ovn-hybrid

Description:
Installs a cluster with a hybrid OVN networking on Azure and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-azure-upgrade

Description:
Installs a cluster with a default configuration on Azure and installs an specified initial version of an operator and then upgrades to the latest bundle from the built index.

Pre: Post:
Name: optional-operators-ci-gcp

Description:
Installs a cluster with a default configuration on GCP and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-gcp-upgrade

Description:
Installs a cluster with a default configuration on GCP and installs an specified initial version of an operator and then upgrades to the latest bundle from the built index.

Pre: Post:
Name: optional-operators-ci-vsphere

Description:
Installs a cluster with a default configuration on vsphere and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-ci-vsphere-ovn-hybrid

Description:
Installs a cluster with hybrid OVN networking on vsphere and installs an optional operator using the built index image that refers to build bundle images.

Pre: Post:
Name: optional-operators-cvp-common-aws

Description:
Installs a cluster with a default configuration on AWS, install an optional operator using the input index image, package and channel, and execute a common suite of CVP tests to validate the optional operator. Important: Parameter values in `env` are supposed to be used only in rehearsals and serve as "testing defaults". Production jobs should always override them via `cvp-trigger`.

Pre: Test: Post:
Name: optional-operators-cvp-common-claim

Description:
This workflows perform shared pre/post actions on clusters obtained from preinstalled pools (https://docs.ci.openshift.org/docs/architecture/ci-operator/#testing-with-a-cluster-from-a-cluster-pool). The intent of this workflow is to mimic the `ipi-$PLATFORM` workflow behavior, just without the installation/deprovision steps.

Pre: Test: Post:
Name: optional-operators-cvp-common-ibmz-eco

Description:
Installs a cluster with a default configuration on IBM Z, install an optional operator using the input index image, package and channel, and execute a common suite of CVP tests to validate the optional operator. Important: Parameter values in `env` are supposed to be used only in rehearsals and serve as "testing defaults". Production jobs should always override them via `cvp-trigger`.

Pre: Test: Post:
Name: optional-operators-cvp-common-powervs

Description:
Installs a cluster with a default configuration on power, install an optional operator using the input index image, package and channel, and execute a common suite of CVP tests to validate the optional operator. Important: Parameter values in `env` are supposed to be used only in rehearsals and serve as "testing defaults". Production jobs should always override them via `cvp-trigger`.

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-api-machinery

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-apps

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-arch

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-auth

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-cli

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-instrumentation

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-network

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-node

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-scheduling

Description:

Pre: Test: Post:
Name: redhat-et-microshift-e2e-openshift-conformance-sig-storage

Description:

Pre: Test: Post:
Name: shiftstack-cleanup

Description:
Prune resources on the CI clouds.

Pre: Test:
Name: shiftstack-monitor

Description:
Monitor resources on the CI clouds and publish metrics.

Pre: Test:
Name: shiftstack-quotas

Description:
Check that CI clouds are not running on low quotas and if it's the case, report which resources are low.

Pre: Test:
Name: telco-bastion

Description:
Install a cluster through an ssh bastion service for telco testing

Pre:
Name: upi-azurestack

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

Pre: Post:
Name: upi-gcp

Description:
The UPI 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 `upi-gcp-{pre,post}` chains to allow other workflows to mimic and extend this base workflow without a need to backport changes.

Pre: Post:
Name: upi-gcp-nested

Description:
The UPI workflow provides pre- and post- steps that provision and deprovision an OpenShift cluster with a default configuration on a VM which have nested virtualization enable and present 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 `upi-gcp-nested-{pre,post}` chains to allow other workflows to mimic and extend this base workflow without a need to backport changes.

Pre: Post:
Name: upi-gcp-rhel8

Description:
The UPI workflow provides pre- and post- steps that provision and deprovision a rhel8 gcp instance allowing job authors to inject their own binaries and end-to-end test logic. All modifications to this workflow should be done by modifying the `upi-gcp-rhel8-{pre,post}` chains to allow other workflows to mimic and extend this base workflow without a need to backport changes.

Pre: Post:
Name: upi-gcp-xpn

Description:
The UPI 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 `upi-gcp-{pre,post}` chains to allow other workflows to mimic and extend this base workflow without a need to backport changes.

Pre: Post:
Name: upi-ibmz-eco

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

Pre: Post:
Name: upi-powervs

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

Pre: Post:
Name: upi-vsphere

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

Pre: Post:

Chains

Chains are registry components that allow users to string together multiple registry components under one name. These components can be steps and other chains.

Name Description Steps
baremetalds-assisted-operator Installing Assisted Service Operator on top of a baremetal cluster.
baremetalds-assisted-operator-before-upgrade Installing Assisted Service Operator on top of a baremetal cluster.
baremetalds-assisted-setup Checkout and execute assisted-test-infra on a packet server
baremetalds-ipi-post The Baremetalds IPI cleanup chain contains all steps that gather and teardown an OpenShift cluster on Baremetal, provisioned by the `baremetald-ipi-pre` chain.
baremetalds-ipi-pre The Baremetald IPI setup chain contains all steps that provision an OpenShift cluster with a default configuration on bare metal.
gather The gather step chain contains all the individual steps necessary to gather artifacts from a cluster.
gather-core-dump The network step runs the must gather network tool to gather core dumps.
gather-network The network step runs the must gather network tool to gather network artifacts.
hypershift-launch-aws-create
hypershift-launch-aws-destroy
ipi-aws-ovn-pre The IPI-OVN pre chain contains all steps that provision an OpenShift cluster with a configuration that enables OVN networking
ipi-aws-post The IPI cleanup step contains all steps that gather and deprovision an OpenShift cluster on AWS, provisioned by the `ipi-aws-pre` chain.
ipi-aws-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on AWS.
ipi-aws-pre-manual-oidc-sts The IPI setup step contains all steps that provision an OpenShift cluster with user defined OIDC provider and IAM roles on AWS for operators.
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.
ipi-aws-pre-sharednetwork The IPI setup step contains all steps that provision an OpenShift cluster in a shared VPC configuration on AWS.
ipi-aws-pre-stableinitial The IPI setup step contains all steps that provision an OpenShift cluster from stable-initial imagestream with a default configuration on AWS.
ipi-aws-pre-techpreview The IPI setup step contains all steps that provision an OpenShift cluster in a Tech Preview configuration on AWS.
ipi-aws-pre-workers-rhel The worker RHEL setup step contains all steps that add RHEL workers to an existing cluster
ipi-azure-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on Azure, provisioned by the `ipi-azure-pre` chain.
ipi-azure-post-resourcegroup The IPI deprovision step contains all steps that deprovision an OpenShift cluster in an existing Resource Group configuration on Azure.
ipi-azure-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on Azure.
ipi-azure-pre-resourcegroup The IPI setup step contains all steps that provision an OpenShift cluster in an existing Resource Group configuration on Azure.
ipi-azure-pre-sharednetwork The IPI setup step contains all steps that provision an OpenShift cluster in a shared Virtual Network configuration on Azure.
ipi-azure-pre-stableinitial The IPI setup step contains all steps that provision an OpenShift cluster from stable-initial imagestream with a default configuration on Azure.
ipi-azure-pre-techpreview The IPI setup step contains all steps that provision an OpenShift cluster in a Tech Preview configuration on Azure.
ipi-azurestack-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on Azure Stack Hub, provisioned by the `ipi-azurestack-post` chain.
ipi-azurestack-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on Azure Stack Hub .
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.
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-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-conf-aws-sharednetwork The IPI AWS configure step generates the AWS-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-aws-techpreview The IPI configure step chain generates the install-config.yaml file based on the cluster profile and optional input files. This configuration will create a cluster with a TechPreviewNoUpgrade FeatureGate installed.
ipi-conf-azure The IPI Azure configure step generates the Azure-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azure-resourcegroup The IPI Azure configure step generates the Azure-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azure-sharednetwork The IPI Azure configure step generates the Azure-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azure-techpreview The IPI configure step chain generates the install-config.yaml file based on the cluster profile and optional input files. This configuration will create a cluster with a TechPreviewNoUpgrade FeatureGate installed.
ipi-conf-azurestack The IPI ASH configure step generates the Azure Stack Hub specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-gcp 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-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-conf-kubevirt This step configures an install-config.yaml file to depoloy to the KUBEVIRT 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 KUBEVIRT project. The resulting file remains in the shared directory for future consumption.
ipi-conf-kubevirt-networktype This step configures an install-config.yaml file to depoloy to the KUBEVIRT 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 KUBEVIRT project. The resulting file remains in the shared directory for future consumption.
ipi-conf-openstack The ipi-conf-openstack chain contains all the refs and chains necessary to configure the system before deploying an IPI installation of OpenShift onto OpenStack. ipi-conf-openstack-noramfs is identical to this chain, except that it omits the ipi-conf-etcd-on-ramfs step.
ipi-conf-openstack-noramfs The ipi-conf-openstack-noramfs chain is identical to the ipi-conf-openstack except that it omits the ipi-conf-etcd-on-ramfs step. It contains all the refs and chains necessary to configure the system before deploying an IPI installation of OpenShift onto OpenStack
ipi-conf-openstack-techpreview The ipi-conf-openstack-techpreview chain contains all the refs and chains necessary to configure the system before deploying an IPI installation of OpenShift onto OpenStack. This configuration will create a cluster with a TechPreviewNoUpgrade FeatureGate installed.
ipi-conf-ovirt The IPI configure step chain generates the install-config.yaml and ovirt-config.yaml files based on the cluster profile and lease inforamtion.
ipi-conf-ovirt-release-4.4-4.5 The IPI configure step chain generates the install-config.yaml and ovirt-config.yaml files based on the cluster profile and lease information for a release-4.4/4.5 OpenShift cluster.
ipi-conf-ovirt-release-4.6-4.7 The IPI configure step chain generates the install-config.yaml and ovirt-config.yaml files based on the cluster profile and lease information for a release-4.6/4.7 OpenShift cluster.
ipi-conf-vsphere The IPI vSphere configure step generates the vSphere-specific install-config.yaml contents based on the cluster profile, $SHARED_DIR/vips.txt, $SHARED_DIR/basedomain.txt, and optional input files.
ipi-deprovision The IPI deprovision step chain contains all the individual steps necessary to gather and deprovision an OpenShift cluster.
ipi-deprovision-kubevirt The IPI deprovision step chain contains all the individual steps necessary to gather and deprovision an OpenShift cluster.
ipi-deprovision-openstack The ipi-deprovision-openstack contains all the refs and chains necessary to clean up cloud resources after a OpenShift cluster has been destroyed.
ipi-gcp-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on GCP, provisioned by the `ipi-gcp-pre` chain.
ipi-gcp-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on GCP.
ipi-gcp-pre-sharednetwork The IPI setup step contains all steps that provision an OpenShift cluster in a shared network configuration on GCP.
ipi-gcp-pre-stableinitial The IPI setup step contains all steps that provision an OpenShift cluster from stable-initial imagestream with a default configuration on GCP.
ipi-install The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.
ipi-install-kubevirt The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster over kubevirt platform.
ipi-install-libvirt The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.
ipi-install-ovirt The oVirt IPI install step chain contains all the individual steps necessary to install an OpenShift cluster on oVirt.
ipi-install-ovirt-stableinitial The oVirt IPI install step chain contains all the individual steps necessary to install an OpenShift cluster on oVirt.
ipi-install-stableinitial The IPI install-stableinitial step chain contains all the individual steps necessary to install an OpenShift cluster from stable-initial imagestream stream.
ipi-install-vsphere The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.
ipi-install-vsphere-stableinitial The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster on vSphere from "stable-initial" imagestream
ipi-kubevirt-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on KubeVirt, provisioned by the `ipi-kubevirt-pre` chain.
ipi-kubevirt-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on Kubevirt.
ipi-kubevirt-pre-stableinitial The IPI setup step contains all steps that provision an OpenShift cluster from stable-initial imagestream with a default configuration on KubeVirt.
ipi-libvirt-post The IPI cleanup step contains all steps that gather and deprovision an Openshift cluster on multi-arch, provisioned by the 'ipi-libvirt-pre' chain.
ipi-libvirt-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on multi-arch(s390x & ppc64le)
ipi-openstack-post The ipi-openstack-post chain inludes all the refs and chains necessary to tear down an ipi installation of OpenShift on Openstack.
ipi-openstack-pre The ipi-openstck-pre chain contains the necessary refs and chains to prepare the system to run ipi install on OpenStack.
ipi-openstack-pre-noramfs The ipi-openstack-pre-noramfs chain contains the necessary refs and chains to prepare the system to run ipi install on OpenStack without using a ramfs for etcd.
ipi-openstack-pre-stableinitial The ipi-openstack-pre-stableinitial chain contains the necessary refs and chains to prepare the system to run ipi install on OpenStack from release:initial imagestream
ipi-openstack-pre-techpreview The IPI setup step contains all steps that provision an OpenShift cluster in a Tech Preview configuration on OpenStack.
ipi-ovirt-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on oVirt, provisioned by the `ipi-ovirt-pre` chain.
ipi-ovirt-pre The IPI setup step contains all steps that provision an OpenShift cluster with a tmpfs configuration for ETCD, persistent Prometheus storage and no Affinity Groups.
ipi-ovirt-pre-release-4.4-4.5 The IPI setup step contains all steps that provision an OpenShift cluster with a tmpfs configuration on oVirt and no PVC (release 4.4 and 4.5 don't have CSI on oVirt).
ipi-ovirt-pre-release-4.6-4.7 The IPI setup step contains all steps that provision an OpenShift cluster with a tmpfs configuration for ETCD and persistent Prometheus storage.
ipi-ovirt-pre-upgrade The IPI setup step contains all steps that provision an OpenShift cluster with persistent Prometheus storage and no Affinity Groups.
ipi-ovirt-pre-upgrade-release-4.4-4.5 The IPI setup step contains all steps that provision an OpenShift cluster on oVirt and no PVC (release 4.4 and 4.5 don't have CSI on oVirt).
ipi-ovirt-pre-upgrade-release-4.6-4.7 The IPI setup step contains all steps that provision an OpenShift cluster on oVirt.
ipi-vsphere-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on vSphere, provisioned by the `ipi-vsphere-pre` chain.
ipi-vsphere-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on vSphere.
ipi-vsphere-pre-stableinitial The IPI setup step contains all steps that provision an OpenShift cluster from stable-initial imagestream with a default configuration on vSphere.
ocm-e2e-clusterpool-checkout This step checks out hub and managed clusters from the given cluster pools.
openshift-e2e-libvirt-test The LIBVIRT test step executes the common end-to-end test suite.
osd-create Uses ocm to create a cluster in an OSD environment.
osd-delete Uses ocm to delete a cluster from an OSD environment.
redhat-et-microshift-e2e-openshift-conformance-sig-api-machinery
redhat-et-microshift-e2e-openshift-conformance-sig-apps
redhat-et-microshift-e2e-openshift-conformance-sig-arch
redhat-et-microshift-e2e-openshift-conformance-sig-auth
redhat-et-microshift-e2e-openshift-conformance-sig-cli
redhat-et-microshift-e2e-openshift-conformance-sig-instrumentation
redhat-et-microshift-e2e-openshift-conformance-sig-network
redhat-et-microshift-e2e-openshift-conformance-sig-node
redhat-et-microshift-e2e-openshift-conformance-sig-scheduling
redhat-et-microshift-e2e-openshift-conformance-sig-storage
redhat-et-microshift-e2e-pre This step runs microshift and microshift e2e in instance created by upi-install-gcp-nested.
upi-azurestack-post This chain deprovisions all the components created by the upi-azurestack-pre chain.
upi-azurestack-pre This chain contains all of the steps to provision an OpenShift cluster using the Azure Stack Hub UPI workflow.
upi-conf-gcp This step creates the files necessary to deploy a GCP UPI cluster. It requires an existing install-config.yaml to exist in the shared directory with the necessary configuration to deploy a cluster to the GCP CI project. It uses this install-config.yaml to generate the Ignition, metadata.json, and kubeconfig files with the modifications required to support the GCP UPI workflow. These files are copied to the shared directory for future consumption.
upi-conf-ibmz-eco This step creates the files necessary to deploy an IBM Z UPI cluster. It creates a terraform.tfvars file that is used to generate install yaml and ignition files
upi-conf-vsphere This step creates the files necessary to deploy a vSphere UPI cluster. It requires an existing install-config.yaml to exist in the shared directory with the necessary configuration to deploy a cluster to the vSphere CI project. It uses this install-config.yaml to generate the govc.sh, Ignition, metadata.json, and kubeconfig files with the modifications required to support the vSphere UPI workflow. These files are copied to the shared directory for future consumption.
upi-gcp-nested-post This step deprovisions the gcloud deployments created by upi-install-gcp-nested.
upi-gcp-nested-pre This step provision the gcloud deployments created by upi-install-gcp-nested.
upi-gcp-post This chain deprovisions all the components created by the upi-gcp-pre chain.
upi-gcp-pre This chain contains all of the steps to provision an OpenShift cluster using the GCP UPI workflow.
upi-gcp-rhel8-post This step deprovisions the gcloud deployments created by upi-install-gcp-rhel8.
upi-gcp-rhel8-pre This step provision the gcloud deployments created by upi-install-gcp-rhel8.
upi-gcp-xpn-post This chain deprovisions all the components created by the upi-gcp-pre chain.
upi-gcp-xpn-pre This chain contains all of the steps to provision an OpenShift cluster using the GCP UPI workflow.
upi-ibmz-eco-post This chain deprovisions all the components created by the upi-ibmz-eco-pre chain.
upi-ibmz-eco-pre This chain contains all of the steps to provision an OpenShift cluster using the IBM Z UPI workflow.
upi-powervs-post This chain deprovisions all the components created by the upi-powervs-pre chain.
upi-powervs-pre This chain contains all of the steps to provision an OpenShift cluster using the OpenShift on PowerVS UPI workflow.
upi-vsphere-post This chain deprovisions all the components created by the upi-gcp-pre chain.
upi-vsphere-pre This chain contains all of the steps to provision an OpenShift cluster using the vSphere UPI workflow.
workers-rhel The workers rhel step chain contains steps necessary to prepare and configure OCP on RHEL worker hosts.

Steps

Steps are the lowest level registry components, defining a command to run and a container to run the command in.

Name Description
baremetalds-assisted-conf Injects extended test list into e2e-metal-assisted.
baremetalds-assisted-conf-devscripts-extraworkers Configure dev-scripts environment variables NUM_EXTRA_WORKERS outside of DEVSCRIPTS_CONFIG. Configures dev-scripts to create extra VMs but not deploy them in the original cluster if APPLY_EXTRA_WORKERS=false. The defaults are NUM_EXTRA_WORKERS=0 and APPLY_EXTRA_WORKERS=false. For more information on these values refer to https://github.com/openshift-metal3/dev-scripts/blob/master/config_example.sh
baremetalds-assisted-conf-devscripts-ipstack Configure dev-scripts IP_STACK outside of DEVSCRIPTS_CONFIG.
baremetalds-assisted-gather Log gather from remote packet server.
baremetalds-assisted-operator-gather Gathering data about assisted operator environment.
baremetalds-assisted-operator-setup Installing Assisted Service Operator and Hive.
baremetalds-assisted-operator-setup-before-upgrade Installing Assisted Service Operator and Hive.
baremetalds-assisted-operator-upgrade Using OLM, upgrade the Infrastrure Operator to the latest version.
baremetalds-assisted-operator-ztp Using hub-cluster with Assisted Service operator to deploy extra workers as spoke clusters. Installation will be following ZTP flow (Zero Touch Provisioning), meaning no explicit provisioning actions will be made outside of the system.
baremetalds-assisted-operator-ztp-after-upgrade Using Assisted installer running on an OCP hub cluster, install a spoke OCP cluster.
baremetalds-assisted-operator-ztp-before-upgrade Using Assisted installer running on an OCP hub cluster, install a spoke OCP cluster.
baremetalds-assisted-setup Checkout and execute assisted-test-infra on a packet server
baremetalds-assisted-test The Baremtal DS E2E assisted step executes the common end-to-end test suite.
baremetalds-devscripts-conf-ipv4 Run dev-scripts with IPv4-only configuration that uses OpenShiftSDN.
baremetalds-devscripts-conf-virtualmedia Run dev-scripts without a provisioning network, using virtual media for all hosts.
baremetalds-devscripts-gather Gather additional logs specific to baremetal IPI deployments.
baremetalds-devscripts-proxy Installs and configures a squid proxy server for use with dev-scripts.
baremetalds-devscripts-setup Checkout and execute dev-scripts on a packet server
baremetalds-e2e-conf Injects extended test list into e2e-metal-ipi.
baremetalds-e2e-test The Baremtal DS E2E step executes the common end-to-end test suite.
baremetalds-metallb-e2e-test The Baremtal DS E2E step executes the metallb end-to-end test suite.
baremetalds-packet-check This step checks for leaked e2e-metal-ipi packet servers in the project
baremetalds-packet-setup This step performs the setup of the packet server
baremetalds-packet-teardown This step deprovisions the packet server
baremetalds-sno-conf Injects extended test list into baremetalds-sno-test.
baremetalds-sno-gather Log gather from remote packet server.
baremetalds-sno-setup Checkout and execute single-node installation workflow on a packet server
baremetalds-sno-test The Baremtal DS E2E single-node step executes the common end-to-end test suite.
build-github-secrets Add GitHub secrets (http, ssh) to be used in Build tests that clone source from private repositories in the openshift-github-testing organization.
ccm-conf-apply-feature-gate Apply custom featureGate configuration to cluster to enable CCM functionality
ccm-conf-pre-create-feature-gate Apply custom featureGate configuration to cluster to enable CCM + CSI functionality
ccm-must-gather The must-gather step runs the must-gather tool to gather ccm artifacts.
cilium-conf This steps installs Cilium OLM manifests (https://github.com/cilium/cilium-olm)
code-ready-crc-e2e-test This step provision the gcloud deployments created by upi-install-gcp-nested.
code-ready-crc-integration-test This step to run crc integration tests.
code-ready-snc-e2e-test This step provision the snc deployments created by upi-install-gcp-nested.
csi-driver-shared-resource-deploy
csi-driver-shared-resource-e2e Run e2e tests for the Shared Resource CSI Driver.
cucushift-aws-ipi The workflow executes cucushift e2e tests
cucushift-pre
fips-check This step checks if FIPS is enabled in all nodes of the cluster and exit accordingly depending on what value the environment variable ${FIPS_ENABLED} holds.
gather-audit-logs The audit-logs step gathers the log files containing the auditing events emitted by the kube-apiserver and openshift-apiserver on each master node.
gather-aws-console The pre-deprovision artifacts step collects console logs from AWS instances. It gathers console logs for all nodes and machines with a provider ID, as well as any instance IDs listed in ${SHARED_DIR}/aws-instance-ids.txt. aws-instance-ids.txt entries should have a single provider ID per line. Duplicate entries are ok; the step deduplicates before gathering.
gather-core-dump The network step runs the must gather network tool to gather core dumps.
gather-crc This step gather the logs for crc test run.
gather-extra The pre-deprovision artifacts step collects extra, CI-specific artifacts which are either not covered by must-gather or are required to debug clusters that are not healthy enough to complete a must-gather.
gather-gcp-console The pre-deprovision artifacts step collects console logs from GCP instances. It gathers console logs for all nodes and machines with a provider ID, as well as any instance IDs listed in ${SHARED_DIR}/gcp-instance-ids.txt. gcp-instance-ids.txt entries should have a single provider ID per line. Duplicate entries are ok; the step deduplicates before gathering.
gather-libvirt The must-gather step runs the must-gather tool to gather artifacts.
gather-loki The pre-deprovision artifacts step collects logs of all containers captured by loki. Even of containers created but no longer presented in the cluster.
gather-must-gather The must-gather step runs the must-gather tool to gather artifacts.
gather-network The network step runs the must gather network tool to gather network artifacts.
gather-proxy The gather step collects journal logs from the proxy.
gather-snc This step gather the logs for snc test run.
hypershift-launch-wait-for-nodes This step blocks indefinitely until the specified nubmer of nodes have a `Ready` condition value of `True`. It assumes the `KUBECONFIG` environment variable is set as part of a workflow that creates clusters.
identitatem-ci-image-mirror This workflow mirrors an image from the CI Registry to a given image ref.
identitatem-ci-rbac This workflow adds the necessary privileges to the Prow job's namespace so that images can be accessed outside the Prow clusters.
insights-live This step installs the insights secret to the cluster to report support data from the support-operator.
ipi-conf The IPI configure step generates the generic portions of the install-config.yaml file based on optional input files.
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.
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-oidc-creds The IPI oidc-creds configure step adds a authentications.config.openshift.io/cluster object and secrets for each operator using sts webhook identity file.
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-conf-aws-sharednetwork The IPI AWS configure step generates the AWS-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azure The IPI Azure configure step generates the Azure-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azure-arcconformance Runs the Arc Enabled Kubernetes Validation Program[1] suite. [1] https://github.com/Azure/azure-arc-validation.
ipi-conf-azure-arcconformance-region Patch region of the Arc Enabled Kubernetes Validation Program[1] suite. [1] https://github.com/Azure/azure-arc-validation.
ipi-conf-azure-resourcegroup The IPI Azure configure step generates the Azure-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azure-sharednetwork The IPI Azure configure step generates the Azure-specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-azurestack The IPI ASH configure step generates the Azure Stack Hub specific install-config.yaml contents based on the cluster profile and optional input files.
ipi-conf-etcd-on-ramfs This step creates a machine config for the master nodes to use ramfs for etcd
ipi-conf-gcp 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-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-conf-kubevirt This step configures an install-config.yaml file to depoloy to the KUBEVIRT 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 KUBEVIRT project. The resulting file remains in the shared directory for future consumption.
ipi-conf-kubevirt-networktype This step configures an install-config.yaml file to depoloy to the KUBEVIRT 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 KUBEVIRT project. The resulting file remains in the shared directory for future consumption.
ipi-conf-libvirt This step configures an install-config.yaml file to depoloy to the LIBVIRT project. An existing install-config.yaml file should already exist in the ${SHARED_DIR} directory. The file is modified to configure the cluster to run in the LIBVIRT project. The resulting file remains in the shared directory for future consumption.
ipi-conf-manual-creds The IPI manual-creds configure step updates install-config.yaml to set credentialsMode to Manual.
ipi-conf-openstack-enable-octavia The ipi-conf-openstack-enable-octavia amends cloud config to enable Octavia LB support
ipi-conf-openstack-precheck The ipi-conf-openstack-precheck verifies the OpenStack infrastructure is ready for deploying an OpenShift cluster on to it.
ipi-conf-ovirt-generate-csi-test-manifest This step creates the csi-test-manifest.yaml file which will be used to configure the csi test suite.
ipi-conf-ovirt-generate-csi-test-manifest-release-4.6-4.8 This step creates the csi-test-manifest.yaml file which will be used to configure the csi test suite. The release 4.6-4.8 manifest doesn't support volume resizing.
ipi-conf-ovirt-generate-install-config This step creates the install-config file which will be used to create the OpenShift cluster. The install-config disables the affinity groups feature
ipi-conf-ovirt-generate-install-config-params This step creates the ovirt-lease.conf file to configure the parameters for creating the install-config file. The step uses a secret from the oVirt namespace that corresponds to the acquired lease name, which contains the parameters required for creating the install-config.yaml file for the cluster.
ipi-conf-ovirt-generate-install-config-release-4.4-4.5 This step creates an install-config file which will be used to create the OpenShift 4.4/4.5 cluster. The install-config contains the dns_vip which was removed after 4.5
ipi-conf-ovirt-generate-install-config-release-4.6-4.7 This step creates an install-config file which will be used to create the OpenShift 4.6/4.7 cluster. The install config doesn't contain refrences to affinity groups.
ipi-conf-ovirt-generate-ovirt-config This step creates the ovirt config file which is required for the openshift-installer to connect to the oVirt engine.
ipi-conf-ovirt-generate-ovirt-config-insecure This step creates the ovirt config with an insecure connection which is required for the openshift-installer to connect to the oVirt engine.
ipi-conf-techpreview Apply TechPreviewNoUpgrade featureGate configuration to cluster to enable tech preview features
ipi-conf-user-workload-monitoring Configure Cluster Monitoring Operator to enable User Workload Monitoring feature in openshift cluster
ipi-conf-vsphere The IPI vSphere configure step generates the vSphere-specific install-config.yaml contents based on the cluster profile, $SHARED_DIR/vips.txt, $SHARED_DIR/basedomain.txt, and optional input files.
ipi-conf-vsphere-check Using the LEASED_RESOURCE (port group) and the secrets from the vSphere cluster profile, confirm there is no pre-existing virtual machines attached to the leased resource. If virtual machines exist remove them.
ipi-conf-vsphere-dns Uses VIPs in ${SHARED_DIR}/vips.txt to create route53 dns records. Outputs ${SHARED_DIR}/basedomain.txt to ensure consistent basedomain in conf and deprovision steps. Saves batch job to delete DNS records to ${SHARED_DIR}/dns-delete.json for use in deprovisioning, with the hosted zone ID in ${SHARED_DIR}/hosted-zone.txt.
ipi-conf-vsphere-lb This step only proceeds for periodic launch jobs. Uses VIPs in ${SHARED_DIR}/vips.txt to create AWS Network Load Balancer and Target Groups. Outputs ${SHARED_DIR}/nlb_arn.txt and ${SHARED_DIR}/tg_arn.txt for use later during deprovisioning.
ipi-conf-vsphere-vips Using secrets from the vSphere cluster profile, the vSphere VIP setup step reserves IP addresses through IPAM and saves them to $SHARED_DIR/vips.txt for later use in creating DNS records and the install config. They are also needed in deprovisioning to release the reserved VIPs (via the ipi-deprovision-vsphere-vips step).
ipi-deprovision-aws-blackholenetwork The deprovision step tears down the blackholenetwork by destroying its stack.
ipi-deprovision-aws-sharednetwork The deprovision step tears down the sharednetwork by destroying its stack.
ipi-deprovision-azure-resourcegroup The IPI Azure resourcegroup deprovision step deletes the Azure resource group used for resource group.
ipi-deprovision-deprovision The IPI deprovision step tears down the cluster.
ipi-deprovision-deprovision-kubevirt The IPI deprovision step tears down the cluster. This step was duplicated from ipi-deprovision-deprovision-ref.yaml because of the changes in calling the binary openshift-install, that needs the KUBECONFIG of the infra cluster, in order to destroy a tenant cluster.
ipi-deprovision-deprovision-libvirt The IPI deprovision step tears down the cluster. This step was duplicated from ipi-deprovision-deprovision-ref.yaml because of the changes in calling the binary openshift-install, that needs the libvirt-installer of the cluster, in order to destroy a tenant cluster.
ipi-deprovision-proxy The deprovision step tears down the proxy and removes its s3 ignition config.
ipi-deprovision-vsphere-diags Collects diagnostic data from the cluster prior to deprovisioning.
ipi-deprovision-vsphere-dns Releases DNS records via `${SHARED_DIR}/hosted-zone.txt` and `${SHARED_DIR}/dns-delete.json`. The IP addresses were allocated with the ipi-conf-vsphere-dns step.
ipi-deprovision-vsphere-lb Deletes AWS Network Load Balancer and Target Groups by their ARN saved in ${SHARED_DIR}/nlb_arn.txt and ${SHARED_DIR}/tg_arn.txt.
ipi-install-hosted-loki The IPI install loki step deploys logging solution for collecting container logs and sending those to Loki hosted on Grafana Cloud.
ipi-install-hosted-loki-staging The IPI install loki step deploys logging solution for collecting container logs and sending those to Loki hosted on Observatorium and Grafana Cloud.
ipi-install-install The IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster, using the provided cluster profile to choose a target IaaS platform. Anything that needs to be configured using manifests should generate them before this step and put them in the SHARED_DIR so that this step can pull in the manifests. Files with name manifest_(manifest_name).yml|yaml end up in $INSTALL_DIR/manifests, while files with name tls_(tls_asset_name).key|pub end up in $INSTALL_DIR/tls.
ipi-install-install-stableinitial The IPI install step runs the OpenShift Installer from stable-initial imagestream in order to bring up an OpenShift cluster, using the provided cluster profile to choose a target IaaS platform. Anything that needs to be configured using manifests should generate them before this step and put them in the SHARED_DIR with the filename manifest_(manifest_name).yml so that this step can pull in the manifest in.
ipi-install-kubevirt-install The IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster, using the kubevirt provided. This step was duplicated from ipi-install-install-ref.yaml because of the changes in calling the binary openshift-install, that needs the KUBECONFIG of the infra cluster, in order to create a tenant cluster.
ipi-install-libvirt-install The libvirt IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster.
ipi-install-loki The IPI install loki step deploys logging solution for collecting container logs with minimal resource requirements.
ipi-install-monitoringpvc The IPI install monitoringpvc step configures cluster-monitoring operator to save prometheus data in a persistent storage. This would ensure metrics are kept during upgrades.
ipi-install-ovirt-patch-image-registry On 4.4 and 4.5 we don't have CSI Driver so we need to patch that image registry to use emptydir.
ipi-install-ovirt-send-event-to-ovirt-post This step sends an event to the oVirt engine with job details
ipi-install-ovirt-send-event-to-ovirt-pre This step sends an event to the oVirt engine with job details
ipi-install-rbac The pre-installation RBAC step adds necessary privileges for the cluster under test against the build farm.
ipi-install-times-collection The IPI install step picks up the cluster installation start and end times to add it to the openshift-install configmap in the openshift-config namespace.
ipi-install-vsphere-registry Once the cluster is running the registry must be patched to set management state and storage to emptydir
ipi-kubevirt-pre-cleanworkspace This step cleaning the workspace before creating any resources for tenant cluster
network-calico This steps installs calico manifests (https://www.projectcalico.org/)
network-conf-disable-cno This steps sets `networkType: None` and disables `cluster-network-operator` (CNO)
ocm-ci-fastforward This workflow fast forwards a source branch to a destination branch in a GitHub repo.
ocm-ci-image-mirror This workflow mirrors an image from the CI Registry to a given image ref.
ocm-ci-rbac This workflow adds the necessary privileges to the Prow job's namespace so that images can be accessed outside the Prow clusters.
ocm-e2e-clusterpool-checkin This step checks clusters back in to the cluster pool. The cluster claims to check in are listed in the file specified by CLUSTER_CLAIM_FILE the SHARED_DIR. If this file is missing no clusters will be checked in. If a cluster claim is removed from the file, it will not be checked in.
ocm-e2e-clusterpool-checkout This step checks out hub and managed clusters from the given cluster pools.
ocm-e2e-clusterpool-cluster-deploy This step deploys ACM on the selected clusters. All name matching is done after stripping the suffix from the cluster claim name. For example, the cluster claim name hub-1-abc12 would be reduced to hub-1 before being matched. Unless CLUSTER_NAMES is set to "none", at least one cluster must be selected for deployment. The latest edge version of ACM for a particular stream (edge or integration) will be deployed first. After this version of ACM is running, the CSV CR for the multiclusterhub-operator will be modified to use the component image from the CI Registry that was built for the PR.
ocm-e2e-clusterpool-cluster-getcreds This step generates credential files for the clusters specified by the cluster claim names in the file specified by CLUSTER_CLAIM_FILE. The credential files will be stored in the SHARED_DIR. The cluster name is taken from the cluster claim name in CLUSTER_CLAIM_FILE and stripping off the trailing suffix. For example, hub-1-abc12 would become hub-1. The kubeconfig file name is made by taking the cluster name and adding a .kc extension. For example, the cluster claim name hub-1-abc12 would give the kubeconfig file name "hub-1.kc" and be stored in 'SHARED_DIR/hub-1.kc'. The metadata file name is made by taking the cluster name and adding a .json extension. For example, the cluster claim name hub-1-abc12 would give the metadata file name "hub-1.json" and be stored in 'SHARED_DIR/hub-1.json'.
ocm-e2e-clusterpool-list This step queries the cluster pool host for a list of available cluster pools, potentially filters and sorts the list of cluster pools, and then writes that list to a file in SHARED_DIR.
ocm-e2e-kind-create This step creates AWS VM created to run KinD based tests. The IP address for the VM is stored in ${SHARED_DIR}/public_ip. The SSH private key is stored in ${SHARED_DIR}/private.pem. Because of the way Prow creates the shared directory, the private key file will have 644 permissions when your test starts. You will need to run `chmod 400 "${SHARED_DIR}/private.pem"` before you use the private key file with ssh.
ocm-e2e-kind-destroy This step destroys the AWS VM created to run KinD based tests.
openshift-cluster-bot-rbac Creates policy allowing cluster-bot the ability to poll for status of cluster operations in this namespace.
openshift-e2e-gcp-crc-test This step executes CodeReady Containers specific tests.
openshift-e2e-gcp-libvirt-cert-rotation-conf Injects registry setup and install script into gcp instance for libvirt mirrored registry nested installs.
openshift-e2e-gcp-libvirt-cert-rotation-setup This is to setup a nested openshift cluster using libvirt provider.
openshift-e2e-gcp-libvirt-cert-rotation-test This step runs e2e certificate rotation test in a libvirt cluster.
openshift-e2e-gcp-libvirt-conf Injects extended test list into gcp instance for libvirt nested installs.
openshift-e2e-gcp-libvirt-setup This step is to setup a nested openshift cluster using libvirt provider.
openshift-e2e-gcp-libvirt-test This step is to run e2e test for libvirt provider.
openshift-e2e-libvirt-conf Injects extended test list or exclude list.
openshift-e2e-libvirt-test The LIBVIRT test step executes the common end-to-end test suite.
openshift-e2e-ovirt-cleanup-test ovirt infra cleanup script
openshift-e2e-ovirt-minimal-test The Openshift E2E step executes the common end-to-end test suite - this step will become a PR to the general e2e tests script, created this step to avoid triggering all e2e jobs.
openshift-e2e-ovirt-prfinder-test ovirt infra prfinder tool, creates a connection between the originating PR and the oVirt infrastructure, PR link is displayed on the oVirt CI portal under VM comment.
openshift-e2e-test The Openshift E2E step executes the common end-to-end test suite.
openshift-e2e-test-capabilities-check The Openshift E2E capabilitie check verifies whether NET_RAW is enabled in the restricted scc based on if the capabilities MC exists or not.
openshift-kubernetes-e2e-test The Kubernetes E2E step executes the kube end-to-end test suite.
openshift-manifests-cgroupsv2 This steps adds MachineConfigs which configure nodes to use cgroupsv2
openshift-perfscale-configmap-scale This step runs the perfscale configmap-scale workload in the deployed cluster
openshift-psap-ci-artifacts-aws-gpu The OpenShift-PSAP CI_Artifacts gpu step creates a new machineset with a GPU instance type.
openshift-release-analysis-aggregator Launches the job-run-aggregator to analyze the release analysis jobs launched by the release-controller.
openstack-conf-clouds The ipi-conf-openstack ref writes all the environmental variables required to run an ipi installation of OpenShift on OpenStack to the ${SHARED_DIR} directory.
openstack-conf-creatednsrecords This steps creates the required dns records for the ingress and api FIPS. Expects the following to exist ${SHARED_DIR}/API_IP, ${SHARED_DIR}/INGRESS_IP, and ${SHARED_DIR}/CLUSTER_NAME. Creates ${SHARED_DIR}/api-record.json and ${SHARED_DIR}/ingress-record.json.
openstack-conf-createfips Creates two floating IPs in OPENSTACK_EXTERNAL_NETWORK with the description set to "${SHARED_DIR/CLUSTER_NAME".api-fip and "${SHARED_DIR/CLUSTER_NAME".ingress-fip. Writes IP and UID of created FIPs to $SHARED_DIR for later reference.
openstack-conf-exportcindercredentials Prepares a file to export the OpenStack credentials for Cinder.
openstack-conf-generateconfig Generates the necessary install-config.yaml file based on the requested CONFIG_TYPE. Saves the file as ${SHARED_DIR}/install-config.yaml. Load balancer IP and cluster name, are expected to be in ${SHARED}/API_IP and ${SHARED_DIR}/CLUSTER_NAME respectively. This ref is compatible with OCP 4.6+ and will break 4.5, because `ingressFloatingIP` was only introduced in 4.6.
openstack-conf-resourcenames Selects the values for OPENSTACK_EXTERNAL_NETWORK, OPENSTACK_COMPUTE_FLAVOR and ZONES based on a matrix that uses CLUSTER_TYPE. Also generates a safe CLUSTER_NAME. All values are persisted in $SHARED_DIR.
openstack-deprovision-bastionproxy This step deletes the bastion proxy.
openstack-deprovision-deletednsrecords This steps deletes the dns records created by the test. Expects ${SHARED_DIR}/api-record.json and ${SHARED_DIR}/ingress-record.json to exists.
openstack-deprovision-deletefips Delete the api and ingress fips previously created by the pre steps. Expects ${SHARED_DIR}/DELETE_FIPS to exist.
openstack-deprovision-machinesubnet This step removes the machine subnet, its network and router as well.
openstack-gather Gather platform-specific diagnostic information about the cluster.
openstack-noop This step does nothing and can be used as a test override.
openstack-provision-bastionproxy This step creates the bastion proxy when $CONFIG_TYPE is byon.
openstack-provision-machinesubnet This step creates the necessary resources for user-provided custom subnet when $CONFIG_TYPE is byon. It creates a network named "${CLUSTER_NAME}-network". Then it adds to it a subnet named "${CLUSTER_NAME}-subnet" and creates a router named "${CLUSTER_NAME}-router". It attaches the router to the subnet of the $OPENSTACK_EXTERNAL_NETWORK. Finally, it writes their UIDS to ${SHARED_DIR}.
openstack-provision-virtual THIS IS A PLACEHOLDER. This workflow provisions a virtual machine where to test the OpenStack-provisioning scripts.
openstack-test-manifests Runs the manifest-generation tests for OpenStack.
operator-pipelines-preflight-common-check This step will execute the Preflight utility against a target certification test asset. Preflight STDOUT is suppressed, and log file always pushed to the SHARED_DIR as a tarball called preflight.tar.gz. This is to encourage the secure transmission of those assets in a follow up step for this task. Optionally, setting PUBLISH_ARTIFACTS=true when calling this task will immediately push preflight artifacts and logfiles to the ARTIFACT_DIR which is searchable on prow.ci.openshift.org.
operatorhub-subscribe The subscribe step installs an optional operator on the OperatorHub from a provided package and channel.
optional-operators-ci-upgrade The upgrade step upgrades an optional operator installed by the subscribe step.
optional-operators-configure-proxy-registry The configure-proxy registry step configures the proxy image registry to pull internal images.
optional-operators-configure-realtime-tuned-profile The configure-realtime-tuned-profile step applies realtime tuned profile to cluster workers.
optional-operators-cvp-common-apply-secrets Collect the project information from the supplied Pyxis project URL, decrypt the encrypted kube_objects and apply the kube_objects on the testing cluster before the opereator is installed and tested.
optional-operators-cvp-common-probe This steps serves as an frequently-executed probe that verifies OpenShift CI generally works and certain externally observed behavior does not change. The probe will attempt to access bundle and index images (testing that OpenShift CI can access internal images via authenticated proxy) and then save values of all parameters to a well-known artifact (so it can be verified that parameter passing works and artifact placement did not change).
optional-operators-cvp-common-scorecard The operator cvp scorecard test for bundle images from brew registry.
optional-operators-cvp-common-test The shared CVP tests to validate optional operator images.
optional-operators-subscribe The subscribe step installs an optional operator from a provided index image.
osd-create-create The cluster creation step uses ocm to create an OSD cluster using the provided cluster profile. The cluster profile should include an sso-client-id and sso-client-secret to login. The cluster profile should also include .awscred and aws-account-id (presently OSD only supports AWS). If the clusterExpects $SHARED_DIR/ocm-cluster-create-args to contain additional (cloud platform specific) arguments to pass on the ocm create command line. Platform specific arguments might for AWS: --compute-machine-type=.. --aws-account-id=.. --aws-secret-key-id=.. --aws-secret-access-key=..
osd-delete-delete Deletes a cluster in an OSD environment using ocm.
ovn-conf The ovn configure step changes the networkType from OpenshiftSDN to OVNKubernetes in the install-config.yaml It will also create a configMap with a gateway-mode config if ${GATEWAY_MODE} exists
ovn-conf-dualstack The ovn dualstack conf step adds the configuration for dualstack to set of manifests for installation
ovn-conf-hybrid-manifest The ovn hybrid manifest step adds the configuration for the hybrid networking to set of manifests for installation
ovn-conf-hybrid-manifest-with-custom-vxlan-port The ovn hybrid manifest step adds the configuration for the hybrid networking with vxlan port set to 9789 in manifests for installation
ovn-conf-ipsec-manifest The ovn ipsec manifest step adds the configuration for ipsec to set of manifests for installation
ovn-sdn-migration The step changes the networkType from OpenshiftSDN to OVNKubernetes in a running cluster
ovn-sdn-migration-rollback The step rollback the networkType from OVNKubernetes to OpenShiftSDN in a running cluster
redhat-et-microshift-e2e-openshift-conformance-sig-api-machinery
redhat-et-microshift-e2e-openshift-conformance-sig-apps
redhat-et-microshift-e2e-openshift-conformance-sig-arch
redhat-et-microshift-e2e-openshift-conformance-sig-auth
redhat-et-microshift-e2e-openshift-conformance-sig-cli
redhat-et-microshift-e2e-openshift-conformance-sig-instrumentation
redhat-et-microshift-e2e-openshift-conformance-sig-network
redhat-et-microshift-e2e-openshift-conformance-sig-node
redhat-et-microshift-e2e-openshift-conformance-sig-scheduling
redhat-et-microshift-e2e-openshift-conformance-sig-storage
redhat-et-microshift-e2e-pre This step runs microshift and microshift e2e in instance created by upi-install-gcp-nested.
redhat-et-microshift-e2e-run
redhat-et-microshift-e2e-wait-for-cluster-up
sdn-conf The sdn configure step sets the networkType to OpenShiftSDN in the install-config.yaml
sdn-conf-multi-manifest The SDN multi-manifest step adds the configuration for SDN multi-tenant networking to set of manifests for installation. The script creates the manifest_cluster-network-03-config.yml file that is consumed by ipi-install-install.
shiftstack-bugwatcher-pretriage Assigns untriaged bugs and notifies on Slack.
shiftstack-cleanup Prune resources on the CI clouds.
shiftstack-gazelle Perform some basic root cause analysis on ShiftStack periodics, then publish the results in a spreadsheet.
shiftstack-monitor Monitor resources on the CI clouds and publish metrics.
shiftstack-monitor-expose Uploads metrics from $SHARED_DIR to a well-known Swift container.
shiftstack-quotas Check that CI clouds are not running on low quotas and if it's the case, report which resources are low.
single-node-conf-aws Modifies install-config.yaml to use a single control-plane node and without any workers.
single-node-conf-azure Modifies install-config.yaml to use a single control-plane node and without any workers.
single-node-conf-e2e Configurations required to run E2E tests on a single node cluster.
single-node-conf-e2e-graceful-shutdown Configurations required to run E2E graceful shutdown tests on a single node cluster.
single-node-conf-gcp Modifies install-config.yaml to use a single control-plane node and without any workers.
single-node-e2e-test The Openshift E2E step executes the common end-to-end test suite.
ssh-bastion The post-installation ssh-bastion step adds an ssh bastion to an exiting cluster.
storage-conf-csi-aws-ebs The csi-aws-ebs step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for AWS EBS CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-conf-csi-azure-disk The csi-azure-disk step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for Azure Disk CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-conf-csi-gcp-pd The csi-gcp-pd step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for GCP PD CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-conf-csi-openstack-cinder The csi-openstack-cinder step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for OpenStack Cinder CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-conf-csi-openstack-manila The csi-openstack-manila step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for OpenStack Manila CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-conf-csi-vsphere The csi-vsphere step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for vSphere CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-conf-feature-gate The feature-gate step enables given FeatureGate.Spec.FeatureSet in a running cluster.
storage-conf-wait-for-csi-driver The storage-conf-wait-for-csi-driver step waits for a given CSI driver to be fully deployed. Since each ClusterCSIDriver uses different conditions, list of the conditions to wait for must be provided. Unfortunately, it's not possible to wait for a condition to get False, e.g. Progressing=False. The driver may not be fully deployed, however, at least one node has the CSI driver installed.
storage-conf-wait-for-csi-migration storage-conf-csi-migration-enable steps enables alpha feature gates for CSI migration of all in-tree volume plugins we have in OCP and waits for the chanegs to be reflected in kube-controller-manager and nodes. It expects that there is no volume present on the system that would be affected by the migration!
storage-create-csi-aws-efs The csi-aws-efs step creates ${SHARED_DIR}/${TEST_CSI_DRIVER_MANIFEST} for AWS EFS CSI driver, which is consumed by openshift-e2e-test step to run CSI driver certification suite.
storage-obj-check This step compares existing storage objects (PVs, StorageClasses, CSIDrivers) in the cluster with objects saved in storage-obj-save step to ensure that e2e tests don't leave any stray objects behind and all volumes are deleted.
storage-obj-save This step saves existing storage objects (PVs, StorageClasses, CSIDrivers) after cluster installation. These objects are used by storage-obj-check step to tell which of them existed before e2e tests started and which are leftovers of the e2e tests.
telco-bastion-setup Install a cluster through an ssh bastion service for telco testing
upi-conf-gcp This step creates the files necessary to deploy a GCP UPI cluster. It requires an existing install-config.yaml to exist in the shared directory with the necessary configuration to deploy a cluster to the GCP CI project. It uses this install-config.yaml to generate the Ignition, metadata.json, and kubeconfig files with the modifications required to support the GCP UPI workflow. These files are copied to the shared directory for future consumption.
upi-conf-gcp-xpn This step creates XPN specific configuration files in SHARED_DIR. These files are consumed by upi-conf-gcp and upi-install-gcp to deploy an XPN cluster.
upi-conf-ibmz-eco This step creates the files necessary to deploy an IBM Z UPI cluster. It creates a terraform.tfvars file that is used to generate install yaml and ignition files
upi-conf-vsphere This step creates the files necessary to deploy a vSphere UPI cluster. It requires an existing install-config.yaml to exist in the shared directory with the necessary configuration to deploy a cluster to the vSphere CI project. It uses this install-config.yaml to generate the govc.sh, Ignition, metadata.json, and kubeconfig files with the modifications required to support the vSphere UPI workflow. These files are copied to the shared directory for future consumption.
upi-conf-vsphere-ova vSphere OVA checks if appropriate template exists. If it does not exist download the ova and upload to vCenter.
upi-deprovision-azurestack This step deprovisions the gcloud deployments created by upi-install-azurestack. It requires the ipi-deprovision step already be executed against the cluster.
upi-deprovision-gcp This step deprovisions the gcloud deployments created by upi-install-gcp. It requires the ipi-deprovision step already be executed against the cluster.
upi-deprovision-ibmz-eco This step deprovisions a UPI cluster on the IBM Z Ecosystem Cloud.
upi-deprovision-powervs This step destroys a OCP cluster running at IBM Cloud on PowerVS.
upi-deprovision-vsphere This step deprovisions the vsphere deployments created by upi-install-vsphere. It requires the ipi-deprovision step already be executed against the cluster.
upi-gcp-nested-post This step deprovisions the gcloud deployments created by upi-install-gcp-nested.
upi-gcp-nested-pre This step provision the gcloud deployments created by upi-install-gcp-nested.
upi-gcp-rhel8-post This step deprovisions the gcloud deployments created by upi-install-gcp-rhel8.
upi-gcp-rhel8-pre This step provision the gcloud deployments created by upi-install-gcp-rhel8.
upi-install-azurestack This step deploys a UPI cluster to the CI Azure Stack Hub project.
upi-install-gcp This step deploys a UPI cluster to the CI GCP project. It requires properly configured Ignition, metadata.json, and kubeconfig files to exist in the shared directory. These files are used to deploy a cluster to the GCP project using the UPI workflow.
upi-install-ibmz-eco This step deploys a UPI cluster to the IBM Z Ecosystem Cloud, under the CI ibmz-eco project. It requires properly configured terraform.tfvars, clouds.yaml, and pull-secret. install-config.yaml and ignition files are generated as part of the installation. These files are used to deploy a cluster to the IBM Z project using the UPI workflow.
upi-install-powervs This step deploys a OCP Cluster at IBM Cloud on PowerVS.
upi-install-vsphere This step deploys a UPI cluster to the CI vSphere project. It requires properly configured govc.sh, Ignition, metadata.json, and kubeconfig files to exist in the shared directory. These files are used to deploy a cluster to the vSphere project using the UPI workflow.
windows-e2e-operator-test The Windows Machine Config Operator's end to end test suite
windows-e2e-operator-test-with-custom-vxlan-port The Windows Machine Config Operator's end to end test suite with custom vxlan port for hybrid-overlay
windows-e2e-playbook-test The Windows Scale Up Ansible playbook's end to end test suite for 4.4/4.5 clusters. Running these tests against other OpenShift versions is not supported.
workers-rhel-aws-provision The post-installation provision step creates new machinesets which provision new RHEL instances for worker nodes.
workers-rhel-repos The post-installation repos step configures repos and host settings for new RHEL instances.
workers-rhel-scaleup The post-installation scaleup step installs and configures OCP on new RHEL instances.

Source code for this page located on GitHub