Validated patterns explained

Learn the basics of validated patterns, a type of flexible code architecture that allows you to go from concept to production using the same stack configuration.

Learn the basics of validated patterns, a type of flexible code architecture that allows you to go from concept to production using the same stack configuration.

Preparing the environment for a validated pattern

10 mins

In this resource, we’ll walk through how to prepare your environment to deploy a validated pattern, which will involve cluster sizing considerations and cluster creation. 

If you plan on installing a cluster via the Hybrid Cloud Console, get started below.

What will you learn?

  • How to plan your cluster storage for a validated pattern
  • How to install your cluster for a validated pattern

What do you need before starting?

Checking cluster storage

Depending on the pattern you use, you’ll want to check that you have sufficient storage on your cluster. 

  1. Navigate to https://validatedpatterns.io/patterns/ and click on the validated pattern you want to deploy. In this learning path, we’ll be working with the Multicloud GitOps pattern.

    Validated patterns will look like this:
     

    The Multicloud GitOps pattern is identified as a validated pattern by the green “Validated” button and checkmark.
    The Multicloud GitOps pattern is identified as a validated pattern by the green “Validated” button and checkmark. 
  2. In the right navigation bar, click on Cluster sizing
  3. Confirm that you meet the minimum requirements for: 
    1. General OpenShift requirements
    2. Datacenter HUB requirements
    3. Number of control plane/worker nodes
    4. Instance types
    5. Any other listed requirements

Create a cluster

  1. Install a new cluster with cluster-admin permissions if you have not already done so. You may also use an existing cluster for this learning path. There are many options for installing a cluster:
    1. Via the Hybrid Cloud Console
    2. Via the command line interface (CLI) using openshift-installer
    3. Via an Ansible playbook 
    4. Via your own organization’s automation tools.
  2. When installing your cluster, make note of the following information, which you’ll need for your values.yaml file in the next step:
    1. Domain
    2. Cluster name
    3. Worker sizing
  3. Optional: Install a second cluster for a multicloud deployment.

Determine values

The values.yaml file is where you will specify variables for your particular deployment of the validated pattern. Here are a few examples of ways you can specify your values.

  • values-clusterGroup sets values of all clusters in that clusterGroup, including:
    • Namespaces
    • Subscriptions to operators
    • Argo CD applications
    • Managed clusters (used on the HUB cluster only)
  • values-<cloud>-dev sets values that are specific to the cloud provider for clusterGroup dev
    • You can add -<version> to define something specific to a version.
  • values-providerCloud sets values across all clusters on that cloud provider.
  • values-global sets values of all clusters across the pattern.
  • values-secret sets and loads secrets (passwords, e.g.).
    • This values file should never be pushed to your git repository and should only exist in your home directory. 

Now that you’ve prepared your cluster, you are now ready to deploy the validated pattern.

Get more support

*Red Hat supports subscribed Red Hat products used in validated patterns. The codified patterns are distributed as community projects and no additional support beyond subscribed Red Hat products is implied.

Previous resource
Validated patterns
Next resource
Deploy a pattern

This learning path is for operations teams or system administrators

Developers may want to check out the Developer Sandbox to get started with validated patterns. 

Get started on developers.redhat.com

Hybrid Cloud Logo LinkedIn YouTube Facebook Twitter

Products

Tools

Try, buy, sell

Communicate

About Red Hat

We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.