Blueprints Overview
Purpose: For platform engineers, operators, and decision-makers, explains what openCenter blueprints are, how they compose, and how to pick the right combination for a deployment.
Blueprints are deployed through the openCenter-gitops-base repository and are not managed through CLI commands. The openCenter-cli generates FluxCD manifests that reference blueprint configurations in openCenter-gitops-base, but blueprint definitions, service compositions, and policy bundles are maintained in that repository. To inspect or customize blueprints, work directly with openCenter-gitops-base.
What Is a Blueprint
A blueprint is a versioned, opinionated deployment pattern that bundles infrastructure configuration, platform services, security policies, and operational workflows into a single deployable unit. Blueprints are not templates you copy and edit — they are living configurations managed through GitOps that receive updates, security patches, and new capabilities over time.
Each blueprint targets a specific workload type or industry requirement. You start from the openCenter platform foundation, then add the blueprint that matches your use case and operating model.
Blueprint Types
openCenter blueprints fall into three categories. They all build on the same platform foundation:
| Type | What It Does | Examples |
|---|---|---|
| Workload | Extends the openCenter foundation for a specific workload operating model. | Cloud (OpenStack), AI |
| Industry | Layers compliance controls, audit configuration, and operational constraints on top of the openCenter foundation or a workload blueprint. | Healthcare, Finance, Telco |
| Data Services | Adds managed data infrastructure alongside the openCenter foundation or a workload blueprint. | Managed Kafka |
How Blueprints Compose
Blueprints are additive. The openCenter foundation is always present. Workload, industry, and data-services blueprints extend it in different directions.
Industry Blueprint (Healthcare / Finance / Telco)
└── adds compliance policies, audit config, operational constraints
Workload Blueprint (Cloud / AI)
└── adds workload-specific services and configuration
Data Services Blueprint (Streaming / future families)
└── adds managed data infrastructure
openCenter Platform Foundation
└── upstream Kubernetes, FluxCD, security, observability, core services
Data Services blueprints are orthogonal — they deploy on the same cluster regardless of which workload or industry blueprint you chose.
Choosing a Blueprint
| If you need... | Start with... |
|---|---|
| Production Kubernetes with observability and security | openCenter Platform Foundation |
| Private cloud with VMs and containers | Cloud Blueprint (OpenStack) |
| GPU workloads for ML/AI | AI Blueprint |
| HIPAA-aligned controls | Healthcare Blueprint + the openCenter foundation |
| SOC 2 / PCI-DSS / NIST controls | Finance Blueprint + the openCenter foundation |
| Edge-to-core fleet management | Telco Blueprint + the openCenter foundation |
| Managed Kafka | Streaming Blueprint + the openCenter foundation or a workload blueprint |
For the full list with status and service details, see the Blueprint Catalog.