Workflow: optional-operators-ci-aws-ovn-hybrid-custom-vxlan-port

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 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.
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-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
ipi-install The IPI install step chain contains all the individual steps necessary to install an OpenShift cluster.
optional-operators-subscribe The subscribe step installs an optional operator from a provided index image.

Test Steps

No test steps configured.

Post Steps

Name Description
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.

Dependencies

Image Exposed As Override[?] Required By Steps
ci-index OO_INDEX no optional-operators-subscribe
release:latest OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE no ipi-install-install
RELEASE_IMAGE_LATEST no ipi-install-install

Environment

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

Variable Name Variable Content Consumed By Steps
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
GATEWAY_MODE ovn-conf
INITIAL_CHANNEL (For upgrade tests) The name of the initial channel of the operator to track. optional-operators-subscribe
INITIAL_CSV (For upgrade tests) The name of the initial CSV to install. optional-operators-subscribe
OO_CHANNEL The name of the operator channel to track. optional-operators-subscribe
OO_INSTALL_NAMESPACE The namespace into which the operator and catalog will be installed. Special value `!create` means that a new namespace will be created. optional-operators-subscribe
OO_PACKAGE The name of the operator package to be installed. Must be present in the index image referenced by `INDEX_IMAGE`. optional-operators-subscribe
OO_TARGET_NAMESPACES A comma-separated list of namespaces the operator will target. Special, value `!all` means that all namespaces will be targeted. If no OperatorGroup exists in `INSTALL_NAMESPACE`, a new one will be created with its target namespaces set to `TARGET_NAMESPACES`, otherwise the existing OperatorGroup's target namespace set will be replaced. The special value `!install` will set the target namespace to the operator's installation namespace. optional-operators-subscribe
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
TMPDIR A pathname of a directory made available for programs that need a place to create temporary files. (default: /tmp) gather-aws-console
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 "optional-operators-ci-aws-ovn-hybrid-custom-vxlan-port" cluster_2 Pre cluster_0 ipi-conf-aws cluster_1 ipi-install cluster_3 Test cluster_7 Post cluster_6 ipi-aws-post cluster_5 ipi-deprovision cluster_4 gather 0 ipi-conf 1 ipi-conf-aws 0->1 2 ipi-install-monitoringpvc 1->2 3 ovn-conf 2->3 4 ovn-conf-hybrid-manifest-with-custom-vxlan-port 3->4 5 ipi-install-rbac 4->5 6 openshift-cluster-bot-rbac 5->6 7 ipi-install-install 6->7 8 ipi-install-times-collection 7->8 9 optional-operators-subscribe 8->9 10 Intentionally left blank 9->10 11 gather-aws-console 10->11 12 gather-must-gather 11->12 13 gather-extra 12->13 14 gather-audit-logs 13->14 15 ipi-deprovision-deprovision 14->15

GitHub Link:

https://github.com/openshift/release/blob/master/ci-operator/step-registry/optional-operators/ci/aws/ovn/hybrid-custom-vxlan-port/optional-operators-ci-aws-ovn-hybrid-custom-vxlan-port-workflow.yaml

Owners:

Approvers:

Source code for this page located on GitHub