How datum-cloud/datum works
Project type and purpose
• This is a Kubernetes-native control-plane project (“Datum”) written in Go, composed of three main binaries (api server, authorization webhook, controller manager) plus accompanying Kubernetes manifests.
• Its purpose is to provide a portable “Datum” control plane that implements custom APIs (via the generic control plane libraries) and controllers/operators for network and workload management.
File structure
• Top-level directories:
• cmd/… – entrypoints for each binary:
◦ datum-apiserver
◦ datum-authorization-webhook
◦ datum-controller-manager
• config/… – Kubernetes YAML/kustomize configurations for deploying each component.
• pkg/… – shared Go packages (logging, server filters).
• .github/workflows – CI pipelines (build, test, publish).
• Each cmd/<binary>/app folder contains the Go code for that component’s logic (e.g., admission.go, filters, authorizers, controllers).
README for additional insights
• The README clarifies the three key Datum control-plane roles:
• API Server – extends Kubernetes API using generic control plane libraries
• Authorization Webhook – enforces RBAC/authorization rules on Datum resources
• Controller Manager – runs controller loops to reconcile Datum CRDs
• There are operator-focused subprojects (network, workload, GCP infra), but this repo provides the core control-plane binaries and deployment manifests.
Elements
• Datum API Server
• Authorization Webhook Service
• Controller Manager
• etcd
• External Cloud APIs
• API calls from kubectl → API Server
• API Server → admission webhook
• API Server ↔ etcd
• Controller Manager → API Server watcher/listener
• Controller Manager → external cloud services
• Blue for “control-plane components” (API Server, Controller Manager)
• Orange for “admission/authorization”
• Green for “external dependencies” (etcd, cloud APIs)
Detailed but concise
• Side-notes for shared libraries (pkg/) to indicate where common code lives.