Control Plane
The Control Plane is the central brain of the Cogrion platform. Every deployment, every state change, and every agent command flows through it.
What It Does
Catalog Management — Platform engineers register stack templates into the catalog. Tenants browse and deploy from these templates. The Control Plane stores specs, manages versions, and tracks which version each deployed stack came from.
Workspace and Stack Orchestration — When a tenant deploys a stack, the Control Plane translates the intent into a concrete execution plan. It resolves template expressions, sorts resources by their dependency graph, and decides which steps run via Temporal and which get dispatched to the Cluster Agent.
State Tracking — The Control Plane is the authoritative record of what exists and in what state. Every resource, every plan step, and every agent command is recorded here.
How It Relates to Other Services
| Service | Relationship |
|---|---|
| Keycloak | Relies on Keycloak to validate every inbound token. All API calls must carry a valid token issued by the tenant's Keycloak realm. See Keycloak. |
| Temporal | Delegates long-running cloud provisioning work (VPCs, EKS clusters, IAM roles) to Temporal workers. |
| Cluster Agent | Issues commands to the Cluster Agent via a polling model. The agent picks up commands, executes them inside the tenant cluster, and reports results back. |
Go Deeper
- Security → How the Control Plane Validates Requests
- Platform Developer → How Stacks Are Registered and Deployed