Add a New Cluster Profile

This guide walks you through creating a new cluster profile step-by-step, with real examples you can follow.

Quick Overview

Creating a cluster profile involves three main steps:

1. Set up leases - Register cloud resources in openshift/release that tests can reserve
2. Add credentials - Store secrets (cloud keys, SSH keys, etc.) that your tests will need
3. Register the profile - Add a new definition in openshift/release to tell the system about your new profile

Time estimate: Plan for 2 pull requests across different repositories, with review cycles for each.

What Is a Cluster Profile?

Think of a cluster profile as a “recipe” that tells the CI system:

• Which cloud platform to use (AWS, GCP, Azure, etc.)
• What credentials are needed
• How to reserve cloud resources for your tests

Instead of configuring each of these things separately for every test, you create a cluster profile once, and then any test can use it by simply saying “use the aws profile” or “use the gcp-oadp-qe profile.”

What happens when you use a cluster profile in a test:

When you add a cluster_profile to a job or workflow, the CI system automatically:

• Mounts credentials: All your cloud account keys, image registry passwords, and other secrets are automatically available to your test steps at $CLUSTER_PROFILE_DIR
• Reserves cloud resources: The test automatically requests a “lease” (reserved cloud account/project) and makes it available via $LEASED_RESOURCE
• Sets up environment: Important environment variables are automatically set, like:
  • $CLUSTER_TYPE - tells your test what cloud platform it’s running on
  • $IMAGE_FORMAT - format for pulling OpenShift images
  • $KUBECONFIG - path to the cluster’s kubeconfig file
• Imports OpenShift images: All test steps automatically have access to the OpenShift release images they need

The bottom line: Different cluster profiles mainly differ in what credentials they provide. One profile might give you access to AWS account A, while another gives you access to AWS account B or a completely different cloud provider.

Prepare the cloud account

In order for most workflows to operate with the cluster profile, the cloud account must be prepared, including creating a new IAM user as described in the OCP document (AWS, GCP).

In addition to the permissions specified by the OCP documentation, include the following which are required for running tests in the environment:

AWS Policies:

• CloudFormationFullAccess
• AmazonEC2ContainerRegistryFullAccess

GCP Roles:

• Deployment Manager Editor
• Compute Image User
• Role Administrator

The default AWS quotas need to be increased to ensure the AWS account is capable of creating and running multiple clusters at the same time. The Configuring an AWS account section of the OpenShift document include general instructions on configuring the quotas. We make the following recommendations to be requested on us-east-1, us-east-2, us-west-1, us-west-2 regions separately:

• Simple Storage Service (S3): Bucket Limit: 1000
• Amazon Elastic Compute Cloud (Amazon EC2): EC2-VPC Elastic IPs: 500
• Amazon Elastic Compute Cloud (Amazon EC2): Running On-Demand Standard (A, C, D, H, I, M, R, T, Z) instances: 3700
• Amazon Virtual Private Cloud (Amazon VPC): VPCs per Region: 250
• Amazon Virtual Private Cloud (Amazon VPC): NAT gateways per Availability Zone: 200
• Amazon Virtual Private Cloud (Amazon VPC): Internet gateways per Region: 200
• Elastic Load Balancing (ELB): Classic Load Balancers per Region: 250

For GCP, we need to increase the following quotas:

• Cloud Filestore API: Basic HDD (Standard) capacity (GB) per region: 20 TB

Adding a New Cluster Profile

When adding a new cluster_profile, you need to complete three main steps:

1. Add the new leases in Boskos.
2. Provide the credentials for the profile.
3. Register the profile in ci-operator/step-registry/cluster-profiles/cluster-profiles-config.yaml.

Steps (1) and (2) can be accomplished simultaneously with just a single PR. Merge it and wait for your credentials to be synchronized by the periodic-ci-secret-bootstrap job.
Open a separate PR to complete step (3).

The following sections walk you through each step with a real-world example.

Adding New Leases

A lease is a reservation of cloud resources (like AWS accounts or GCP projects) that your tests can use. When a test runs with your cluster profile, it automatically requests a lease so it has access to the cloud resources it needs.

The naming convention: Leases are typically named <profile-name>-quota-slice. For example:

• The aws profile uses aws-quota-slice
• The gcp-oadp-qe profile uses gcp-oadp-qe-quota-slice

What you need to do:

You need to register the actual lease resources with the leasing server (Boskos). This tells the system “here are the cloud accounts/projects that can be used for this lease type.”

File: core-services/prow/02_config/_boskos.yaml

See the Adding a New Type of Resource documentation for details on how to register leases. You can also reference this example PR that shows how leases are registered.

Providing Credentials

Your tests need credentials (like cloud account keys, image registry passwords, etc.) to run. These credentials are stored in a Kubernetes Secret and automatically mounted into your test containers.

How it works:

1. Secret naming: The secret is usually named cluster-secrets-<profile-name>. For example:

   • aws profile → cluster-secrets-aws
   • gcp-oadp-qe profile → cluster-secrets-gcp-oadp-qe

2. Two types of credentials are needed:

   • Platform-provided: Things like central image registry pull secrets that the CI platform team manages
   • Your credentials: Cloud account keys, SSH keys, and other secrets specific to your profile

3. Setting it up:

   Step 1: Create a pull request to openshift/release that adds your secret to the ci-secret-bootstrap configuration. This “seeds” the secret with platform-provided content.

   File: core-services/ci-secret-bootstrap/_config.yaml

   See this example for reference.

   Step 2: Add your custom credentials (cloud keys, SSH keys, etc.) using the self-service portal. When adding secrets in Vault, make sure to set these metadata keys:

   1 2	secretsync/target-namespace: "ci" secretsync/target-name: "cluster-secrets-<your-profile-name>"

   These metadata keys tell the system to automatically sync your Vault secrets into the Kubernetes Secret that your tests will use.

Storing AWS Credentials

If your workflows need to create AWS resources before installing the cluster (like the ipi-aws workflow), you’ll need to store AWS credentials in your cluster profile secret.

Important: The secret must contain a key named .awscred (note the leading dot). The value should be the contents of a standard AWS credentials file.

Format:

1
2
3

[default]
aws_access_key_id=YOUR_ACCESS_KEY_ID
aws_secret_access_key=YOUR_SECRET_ACCESS_KEY

Replace YOUR_ACCESS_KEY_ID and YOUR_SECRET_ACCESS_KEY with your actual AWS credentials.

Storing SSH Key Pairs

Some workflows (like ipi-aws) require SSH keys so you can access and debug CI clusters when needed.

Best practice: Generate a new SSH key pair specifically for CI usage. Don’t reuse your personal SSH keys.

How to store them:

SSH keys are stored in the same Vault secret as your other credentials, but as separate key-value pairs:

• Key name: ssh-publickey
  Value: The contents of your SSH public key file (usually ~/.ssh/id_rsa.pub)

• Key name: ssh-privatekey
  Value: The contents of your SSH private key file (usually ~/.ssh/id_rsa)

Example: If you generate a key pair with ssh-keygen -t rsa -f ci-key, you would:

1. Store the contents of ci-key.pub as the ssh-publickey value
2. Store the contents of ci-key as the ssh-privatekey value

Registering a New Profile

To register a new cluster profile, you need to define a new entry in ci-operator/step-registry/cluster-profiles/cluster-profiles-config.yaml.

Think of this as “telling the system about your new profile” - you’re adding it to the list of profiles that the CI system recognizes:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

cluster_profiles:
- name: aws
  owners:
  - org: openshift
  - org: cri-o
    repos:
    - cri-o
  - konflux:
      cluster_groups:
      - rh-staging
      tenant: testplatform-ci-tenant
  cluster_type: aws
  lease_type: aws-quota-slice
  ip_pool_lease_type: aws-ip-pools
  secret: cluster-secrets-aws

The meaning of each stanza is described below:

• name: name of this cluster profile.
• owners: restricts the usage of the cluster profile to a given organization, organization/repositorys or Konflux tenant. For detailed instructions please refer to the README file.
• lease_type: The lease type determines which cloud resources your tests can use.
  This tells the system which “lease” (reserved cloud resources) to use for your profile.
  IMPORTANT: The name of the lease MUST be the same of what you have chosen in the previous step Adding New Leases.
• cluster_type: the cluster type is used by the OpenShift installer to know which cloud platform it’s working with.
  When a test uses your cluster profile, this tells the system what type of cluster to create. The value set here is passed to tests as the $CLUSTER_TYPE environment variable.
  See Understanding Cluster Type
• ip_pool_lease_type: name of the lease type used for the BYOIP feature, see Using AWS IP Pools (Advanced). This field is OPTIONAL.
• secret: name of the secret that holds the cluster profile information.
  IMPORTANT: The name of the secret MUST be the same of what you have chosen in the previous step Providing Credentials.

You can now open and merge a PR that holds the new profile definition.

Understanding Cluster Type

The cluster type is a string that identifies what kind of cloud platform your tests will run on. This value gets passed to your test containers as the $CLUSTER_TYPE environment variable.

How to choose a cluster type:

• For a completely new platform: Create a unique cluster type name (like gcp-oadp-qe). You’ll likely need to work with the OpenShift installer team to add support for this new platform type.
• For a variant of an existing platform: You can reuse the existing cluster type. For example, if you’re creating a new AWS profile that works the same way as the standard AWS profile, you could use aws as the cluster type.

The cluster type is used by the OpenShift installer and other step registry components to know how to set up your cluster. For example, the ipi-install-install step uses this to determine which cloud provider APIs to call.

Using AWS IP Pools (Advanced)

AWS supports a “Bring Your Own IP” (BYOIP) feature that lets you use your own IP addresses for cost savings. If you want to use this with your cluster profile, you need to:

1. Set up the IP Pool in AWS: Follow AWS’s BYOIP documentation to configure IP pools in each region you’ll use. Note: AWS only supports one IP pool per region.

2. Register IP Pool leases in Boskos: Add configuration in openshift/release for each region. The lease name format should be {cluster-profile-name}-ip-pools-{region}.

   File: core-services/prow/02_config/_boskos.yaml
   Example: See this example

3. Update the profile definition: Add the IP Pool lease name to the cluster profile you have defined in Registering a New Profile

1

ip_pool_lease_type: {cluster-profile-name}-ip-pools-{region}

4. Optional - Custom branch validation: TODO

VPN connection

For platforms that need access to restricted environments, ci-operator supports adding a dedicated VPN connection to each test step. Since this is a requirement of specific platforms, it is triggered by special files in the cluster profile(s) associated with those platforms. This process is transparent to the test command: when a VPN connection is requested at the test level, it is set up automatically by the test platform with no changes required to individual tests.

Cluster profile

VPN connections are requested by the presence of a special file named vpn.yaml in the cluster profile, detected when the test steps are about to be executed. This file should have the following fields:

• image: pull spec of the image to be used for the VPN client container.
• commands: the name of another file in the cluster profile (e.g. openvpn.sh) which contains the VPN client’s entry point script. This script is effectively executed as bash -c "$(<f")", where f is the value associated with the commands key.
• wait_timeout: the maximum amount of time the step script should wait before starting (detailed in the next section). This ensures the steps are not blocked until the test timeout (several hours) expires if any problems occur with the VPN client.

Image

The image used for the VPN client should contain the packages necessary to establish the connection, as well as the bash shell to execute the container’s entry point script.

The pull spec placed in the cluster profile can point to images stored anywhere, but the simplest setup is to build and store them in the central CI cluster. Builds are configured in openshift/release in the supplemental images directory (see for example the OpenVPN image build).

Once the BuildConfig is merged into master and the image is built and tagged, the cluster profile can reference the public pull spec. For the OpenVPN image stream from the example above, that would be:

1
2

image: registry.ci.openshift.org/ci/openvpn:latest
# …

Client container

The container should execute the VPN client to establish the connection. It will reside in the same network namespace as the test container, so no special provisions are necessary to make the networking changes usable by the test program. When executed, the entry point program will be located in the directory where the cluster profile files are mounted, so all secrets will be available and can be referenced with a relative path.

In addition to executing the client, the container has also two synchronization points:

• When the connection has been established and the test script should start, a file named /tmp/vpn/up should be created. For OpenVPN, for example, the following options can be used:

1

openvpn --script-security 2 --route-up '/bin/bash -c "touch /tmp/vpn/up"' …

• The script should watch for the creation of a file indicating that the main test has finished and then exit so that the test can terminate properly. This marker file is created automatically by the CI infrastructure at /logs/marker-file.txt. The client can perform these actions with a script such as:

1
2
3
4
5
6
7

function exit_with_test() {
    until [[ -f /logs/marker-file.txt ]]; do sleep 1; done
    while :; do kill 1; sleep 1; done
}

exit_with_test &
# run the VPN client