Workflow: ipi-aws-volsync-csi

OpenShift cluster configured with volume snapshot and clone capabilities required for VolSync functionality. Default CSI storage configured.

Pre Steps

Name Description
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-install The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.
volsync-csi-conf-aws Volume snapshot and clone capabilities are required for some VolSync functionality. Default CSI storage is configured along with a VolumeSnapshotClass. The VolSync operator is also installed.

Test Steps

No test steps configured.

Post Steps

Name Description
ipi-deprovision The IPI deprovision step chain contains all the individual steps necessary to gather and deprovision an OpenShift cluster.

Dependencies

Image Exposed As Override[?] Required By Steps
release:latest OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE no ipi-install-install
RELEASE_IMAGE_LATEST no ipi-install-install
volsync VOLSYNC_OPERATOR no volsync-csi-conf-aws
volsync-mover-rclone MOVER_RCLONE no volsync-csi-conf-aws
volsync-mover-restic MOVER_RESTIC no volsync-csi-conf-aws
volsync-mover-rsync MOVER_RSYNC no volsync-csi-conf-aws

Environment

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

Variable Name Variable Content Consumed By Steps
BASE_DOMAIN A fully-qualified domain or subdomain name. The base domain of the cloud provider is used for setting baseDomain variable of the install configuration of the cluster. (default: origin-ci-int-aws.dev.rhcloud.com) ipi-conf-aws
COMPUTE_NODE_TYPE The instance type to use for compute nodes (e.g. AWS https://aws.amazon.com/ec2/instance-types/). We use a 4 core worker to match the median configuration of the fleet. (default: m5.xlarge) ipi-conf-aws
FIPS_ENABLED (default: false) ipi-conf
OPENSHIFT_INSTALL_EXPERIMENTAL_DUAL_STACK Using experimental Azure dual-stack support (default: false) ipi-install-install
OPENSHIFT_INSTALL_PRESERVE_BOOTSTRAP Keep bootstrap resources after install. Warning: this should only be used for debugging purposes, and poses a risk to cluster stability. ipi-install-install
SIZE_VARIANT The size of the cluster in one of our supported t-shirt values that is standard across all CI environments. The sizes are: * "" (default) - 4 vCPU, 16GB control plane nodes, default workers * "compact" - 8 vCPU, 32GB control plane nodes, no workers * "large" - 16 vCPU, 64GB+ control plane nodes, default workers, suitable for clusters up to 250 nodes * "xlarge" - 32 vCPU, 128GB+ control plane nodes, default workers, suitable for clusters up to 1000 nodes These sizes are roughly consistent across all cloud providers, but we may not be able to instantiate some sizes in some regions or accounts due to quota issues. ipi-conf-aws
ZONES_COUNT The number of Availability Zones to present in the cluster. This depends on the selected region. (default: 2) ipi-conf-aws

Step Graph

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

GitHub Link:

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

Owners:

Approvers:

Reviewers:

Source code for this page located on GitHub