Blueprint Catalog
Purpose: For platform engineers and decision-makers, provides a scannable reference of every openCenter blueprint with its current status, target audience, and key services.
Catalog
| Blueprint | Type | Status | Audience | Key Services |
|---|---|---|---|---|
| Cloud (OpenStack) | Workload | GA | Platform engineers, operators | Nova, Neutron, Cinder, Glance, Keystone, Ironic, Octavia, Kube-OVN, MariaDB Operator, RabbitMQ |
| AI | Workload | Preview | Platform engineers, ML engineers | GPU Operator, openCenter foundation services + GPU scheduling, resource quotas |
| Healthcare | Industry | GA | Platform engineers, security officers | openCenter foundation + HIPAA-aligned Kyverno policies, audit logging, workload segregation |
| Finance | Industry | GA | Platform engineers, security officers | openCenter foundation + SOC2/PCI/NIST controls, change traceability, recovery workflows |
| Telco | Industry | GA | Platform engineers, network operators | openCenter foundation + edge deployment patterns, multi-cluster fleet management |
| Data Services: Streaming | Family member | GA | Platform engineers, app developers | Strimzi Kafka Operator, Kafka Bridge, MirrorMaker 2, Kafka Exporter |
| Data Services: Databases | Family member | Preview Q2 2026 | Platform engineers, app developers | PostgreSQL Operator (TBD) |
| Data Services: Governance | Family member | Planned Q4 2026 | Platform engineers, data engineers | Schema Registry (TBD) |
| Data Services: CDC | Family member | Planned Q1 2027 | Platform engineers, data engineers | Debezium (TBD) |
Foundation
The openCenter platform foundation is not a blueprint. It is the Kubernetes, GitOps, security, observability, networking, and service-management layer that every blueprint builds on.
See openCenter Platform Foundation for the base capabilities shared across deployments.
Status Definitions
| Status | Meaning |
|---|---|
| GA | Generally available. Supported in production. Covered by SLA. |
| Preview | Available for evaluation. Not yet covered by production SLA. Breaking changes possible. |
| Planned | On the roadmap. Not yet available for deployment. |
Blueprint Composition
Every blueprint builds on the openCenter platform foundation:
Industry Blueprint (Healthcare / Finance / Telco)
└── adds compliance policies, audit config, operational constraints
Workload Blueprint (Cloud / AI)
└── adds workload-specific services and configuration
openCenter Platform Foundation
└── upstream Kubernetes, FluxCD, security, observability, core services
Data Services blueprints are additive — they deploy alongside the platform foundation and any workload blueprint on the same cluster.
Version Compatibility
Blueprints are versioned alongside openCenter-gitops-base tags. A blueprint version is compatible with the platform version it was released with. Check the openCenter-gitops-base repository tags for the current compatibility matrix.