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: 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-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: 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-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: 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-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-ovn-hybrid

Description:
OpenShift Azure cluster configured with Hybrid OVN networking

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-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: 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-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-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-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-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-workers-rhel7

Description:
The OpenShift E2E AWS workflow executes the common end-to-end test suite on AWS with RHEL7 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-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-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-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-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-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-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-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-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-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-openstack-csi

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

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-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-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-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-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-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, exercising an upgrade during the process.

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

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

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

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-azure

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

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

Description:
The Openshift E2E Azure workflow executes the upgrade end-to-end test suite on Azure from stable-initial imagestream with a default cluster configuration, exercising an upgrade during the process.

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

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

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

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: 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-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-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-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.

Pre: Test: Post:
Name: telco-bastion

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

Pre:
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-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-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
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.
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-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-workers-rhel7 The worker RHEL7 setup step contains all steps that add RHEL7 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-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default 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-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-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-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-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-openstack 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.
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-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-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 vSphere IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster. Unlike the other IPI installs, the installer image must include vCenter CA certs.
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-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-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.
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-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-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-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-rhel7 The workers rhel7 step chain contains steps necessary to prepare and configure OCP on RHEL7 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-cvo Run assisted-service waiting for cvo.
baremetalds-assisted-gather Log gather from remote packet server.
baremetalds-assisted-setup Checkout and execute assisted-test-infra on a packet server
baremetalds-devscripts-conf-compact Run dev-scripts without workers to build a compact cluster.
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 Log gather from remote packet server.
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-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
code-ready-crc-e2e-test This step provision the gcloud deployments created by upi-install-gcp-nested.
code-ready-snc-e2e-test This step provision the snc deployments created by upi-install-gcp-nested.
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-hosted-loki The pre-deprovision artifacts step collects logs of all containers captured by Loki hosted on Observatorium. Even of containers created but no longer presented in the cluster.
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.
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-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-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-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-openstack 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.
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-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-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-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-deprovision The IPI deprovision step tears down the cluster.
ipi-deprovision-proxy The deprovision step tears down the proxy and removes its s3 ignition config.
ipi-deprovision-vsphere The IPI deprovision step tears down the cluster. Unlike the other IPI deprovisioning, the installer image must include vCenter CA certs.
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-vips Releases IP addresses from the IPAM server. The IP addresses were allocated with the ipi-conf-vsphere-vips step.
ipi-install-hosted-loki The IPI install loki step deploys logging solution for collecting container logs and sending those to Loki hosted on Observatorium.
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 with the filename manifest_(manifest_name).yml so that this step can pull in the manifest in.
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-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-rbac The pre-installation RBAC step adds necessary privileges for the cluster under test against the build farm.
ipi-install-vsphere The vSphere IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster. Unlike the other IPI installs, the installer image must include vCenter CA certs.
ipi-install-vsphere-registry Once the cluster is running the registry must be patched to set management state and storage to emptydir
openshift-e2e-gcp-crc-test This step executes CodeReady Containers specific tests.
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-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-psap-ci-artifacts-aws-gpu The OpenShift-PSAP CI_Artifacts gpu step creates a new machineset with a GPU instance type.
openstack-conf-creatednsrecords This steps creates the required dns records for the ingress and api FIPS. Expects the following to exist ${SHARED_DIR}/LB_FIP_IP, ${SHARED_DIR}/INGRESS_FIP_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 ${CLUSTER_NAME}.api-fip and ${CLUSTER_NAME}.ingress-fip. Writes IP and UID of created FIPs to ${SHARED_DIR} for later reference.
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}/LB_FIP_IP and ${SHARED_DIR}/CLUSTER_NAME respectively.
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.
operatorhub-subscribe The subscribe step installs an optional operator on the OperatorHub from a provided package and channel.
optional-operators-ci-subscribe The subscribe step installs an optional operator using the index image built by ci-operator.
optional-operators-configure-proxy-registry The configure-proxy registry step configures the proxy image registry to pull internal images.
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.
ovn-conf The ovn configure step changes the networkType from OpenshiftSDN to OVNKubernetes in the install-config.yaml
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
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.
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.
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-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-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-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-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-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-rhel7-aws-provision The post-installation provision step creates new machinesets which provision new RHEL instances for worker nodes.
workers-rhel7-repos The post-installation repos step configures repos and host settings for new RHEL instances.
workers-rhel7-scaleup The post-installation scaleup step installs and configures OCP on new RHEL instances.

Source code for this page located on GitHub