Kubernetes Adapter
Gate cluster changes (manifest apply, scale, config references) with structural risk metadata.
What it does
Gate cluster changes (manifest apply, scale, config references) with structural risk metadata.
How it works
1. Validate intent
Adapter checks structure only (required fields, types, unknown fields). It does not run policy logic.
2. Normalize action
Intent is mapped to a generic NormalizedAction with action type CLUSTER_CHANGE.
3. Evaluate policy
Governor evaluates centrally with fail-closed semantics. Any uncertainty returns deny.
4. Build plan + execute
Execution plan is descriptive. Default path is dry-run and returns planned external calls.
5. Emit evidence
Decision output includes deterministic evidence packet and stable evidence hash.
Why this is useful
Use it for
Production cluster safety and release governance
kubernetesCLUSTER_CHANGEExample intent
{
"action": "scale_deployment",
"cluster": "prod-cluster",
"namespace": "payments",
"deployment": "api",
"replicas": 5,
"requested_by": "deploy-agent"
}
Where to monitor
Integration Runtime View
Adapter health, evaluation outcomes, and dry-run execution traces.
Incidents + Deny Analysis
Investigate denied actions and policy matches with evidence references.
Evidence Docs
Validate evidence hashes and export packets for audits.
Policy Docs
Define allowlists, thresholds, manual gates, and environment controls.
