CobaltCore

Appearance

CobaltCore ​

CobaltCore (C5C3) is a Kubernetes-native OpenStack distribution for operating Hosted Control Planes. This repository delivers everything needed for a self-contained OpenStack control-plane stack: from the declarative infrastructure manifests, through the service operators, to the c5c3-operator orchestration layer — built with the Operator SDK (Go), controller-runtime, and Kubebuilder. The Architecture section shows how the pieces fit together, from the implemented management/target-cluster topology to the multi-cluster picture of the original design.

The Keystone operator is the reference implementation that establishes the patterns — CRD layout, sub-reconciler chain, webhooks, finalizers, instrumentation — replicated by every other service operator. Horizon, Glance, Placement, and Barbican are onboarded on the same scaffolding, and the c5c3-operator ties the services together into a single ControlPlane resource.

Start here ​

What's inside ​

  • Operators. Service operators following a shared sub-reconciler pattern, with Keystone as the reference implementation and the c5c3-operator as the ControlPlane orchestration layer. Horizon, Glance, Placement, and Barbican are onboarded on the same conventions.
  • Shared library. Common types, conditions, config rendering, and Kubernetes helpers in internal/common/, plus the Helm chart, operator packaging, and rotation scripts. See the Backend reference.
  • Infrastructure stack. Declarative FluxCD HelmReleases for OpenBao HA, External Secrets Operator, MariaDB, Memcached, and the Envoy Gateway. See Infrastructure Manifests.
  • CI/CD & container images. GitHub Actions for CI and image builds, plus multi-stage builds for the OpenStack service images, Tempest, and the python-base / venv-builder layers. See the CI Workflow.
  • Test suites. Unit, envtest integration, Chainsaw E2E, Tempest, and Chaos Mesh coverage across the stack — see the Testing reference.

Go deeper ​

  • Architecture — the implemented topology, the layering from Flux stack to ControlPlane orchestration, and the Core Components catalog.
  • Guides — day-2 operations, key rotation, multi-tenant deployment, identity backends, and advanced configuration.
  • Reference — CRDs, reconciler architecture, controller events, metrics, and the infrastructure and CI/CD internals.
  • Future — idea sketches for where the operators could go next.
  • Contributing — onboard a new operator or release, follow the guide conventions, and set up the development environment.

For an AI-assisted tour of the codebase, browse the repository on DeepWiki.