Purpose: For platform engineers and leadership, provides a scannable reference of every blueprint with its current status.
Foundation
Workload
| Blueprint | Status | Description |
|---|
| Cloud (OpenStack) | GA | Kubernetes + OpenStack under one operating model |
| AI | Preview | GPU-ready infrastructure with policy controls |
Industry
| Blueprint | Status | Timeline | Description |
|---|
| Finance | GA | — | SOC2, PCI, NIST compliance controls |
| Healthcare | GA | — | HIPAA compliance, workload segregation |
| Telco | GA | — | Edge-to-core fleet consistency |
| Energy & Utilities | In Development | TBD | NERC CIP compliance, OT/IT segregation |
| Retail & E-Commerce | In Development | TBD | PCI-DSS scoped zones, burst scaling |
| Edge & IoT | In Development | TBD | Lightweight edge clusters, offline GitOps |
Data Services
| Blueprint | Status | Timeline | Description |
|---|
| Streaming (Kafka) | Limited Availability | Q2 2026 | Apache Kafka with Strimzi operator |
| Databases (PostgreSQL) | Preview | Q3 2026 | Managed PostgreSQL with operator-backed lifecycle |
| Schema Registry | Planned | Q4 2026 | Schema versioning and compatibility enforcement |
| CDC | Planned | Q1 2027 | Debezium-based change data capture |
| Redis/Valkey | Deferred | TBD | Managed caching (evaluation stage) |
| RabbitMQ | Deferred | TBD | Managed messaging (evaluation stage) |
Status Definitions
| Status | Meaning |
|---|
| GA | Production-ready, fully supported |
| Limited Availability | Available to select customers, approaching GA |
| Preview | Functional but API/config may change |
| Planned | Committed roadmap item with target quarter |
| In Development | Active design work, no committed timeline |
| Deferred | Evaluated but not on current roadmap |
Foundation Composition
Every blueprint listed above inherits the Platform Foundation. The foundation provides 20+ platform services including observability, security, GitOps tooling, storage, networking, and backup. Blueprints add workload-specific or compliance-specific layers on top.
Versioning
Blueprints are versioned via Git tags on openCenter-gitops-base. Customer clusters pin to a specific tag (e.g., v1.0.0) in their FluxCD GitRepository source. Upgrades are a tag bump in the cluster overlay.