Using the Validated Pattern Operator Background The Validated Pattern Operator was developed in order to take advantage of the automation provided with the validated pattern framework.

Workflow These patterns are designed to be composed of multiple components, and for those components to be used in gitops workflows by consumers and contributors.

Technical Requirements Additional requirements specific to the implementation for all Community, and Validated patterns Must Patterns MUST include one or more Git repositories, in a publicly accessible location, containing configuration elements that can be consumed by the OpenShift GitOps operator (ArgoCD) without supplying custom ArgoCD images.

Community Pattern Requirements tl;dr What are they: Best practice implementations conforming to the Validated Patterns implementation practices Purpose: Codify best practices and promote collaboration between different groups inside, and external to, Red Hat Creator: Customers, Partners, GSIs, Services/Consultants, SAs, and other Red Hat teams Requirements General requirements for all Community, and Validated patterns

Validated Pattern Requirements tl;dr What are they: Technical foundations, backed by CI, that have succeeded in the market and Red Hat expects to be repeatable across customers and segments.

Infrastructure Background Enterprise applications require security, especially in multi-cluster and multi-site environments. Applications require trust and use certificates and other secrets in order to establish and maintain trust.