Workflow: openshift-kubernetes-e2e-aws-serial

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 Steps

Name Description
ipi-install-loki The IPI install loki step deploys logging solution for collecting container logs with minimal resource requirements.
ipi-aws-pre The IPI setup step contains all steps that provision an OpenShift cluster with a default configuration on AWS.

Test Steps

Name Description
openshift-kubernetes-e2e-test The Kubernetes E2E step executes the kube end-to-end test suite.

Post Steps

Name Description
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.
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
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
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
TEST_SUITE The test suite to run. Valid options include: 'serial', 'parallel'. (default: parallel) openshift-kubernetes-e2e-test
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 "openshift-kubernetes-e2e-aws-serial" cluster_3 Pre cluster_2 ipi-aws-pre cluster_0 ipi-conf-aws cluster_1 ipi-install cluster_4 Test cluster_8 Post cluster_7 ipi-aws-post cluster_6 ipi-deprovision cluster_5 gather 0 ipi-install-loki 1 ipi-conf 0->1 2 ipi-conf-aws 1->2 3 ipi-install-monitoringpvc 2->3 4 ipi-install-rbac 3->4 5 openshift-cluster-bot-rbac 4->5 6 ipi-install-install 5->6 7 ipi-install-times-collection 6->7 8 openshift-kubernetes-e2e-test 7->8 9 gather-loki 8->9 10 gather-aws-console 9->10 11 gather-must-gather 10->11 12 gather-extra 11->12 13 gather-audit-logs 12->13 14 ipi-deprovision-deprovision 13->14

GitHub Link:

https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/kubernetes/e2e/aws/serial/openshift-kubernetes-e2e-aws-serial-workflow.yaml

Owners:

Approvers:

Source code for this page located on GitHub