Competition K8s Control Plane is a downstream skill of the CTF Sandbox Orchestrator. It applies when the decisive path in a challenge runs through Kubernetes API permissions or controller behavior and not through a single container alone.
The agent separates manifest intent from live cluster state, identifies the active principal, and follows one API action to the pod, secret exposure or route it produces. Evidence is kept by namespace, service account, verb, resource and owner reference.
What You Get
- A three-stage workflow: map the API trust path, trace mutation to workload state, reduce to the decisive cluster path
- A distinction between read, create, patch, exec and secret access
- A checklist of principal, mutation and effect evidence
- A hand-off to the container-runtime skill for single-container deviations
- A pointer to the cloud metadata skill for instance credential questions
Common Use Cases
- Explaining why a live pod differs from its manifest in a lab cluster
- Mapping a RoleBinding to the API action it permits
- Tracing a controller-created job to the object that triggered it
- Finding which workload consumes a given secret
What Makes It Unique
It keeps the unit of analysis at the cluster object chain: principal, permission, mutated object, resulting workload. Admission and controller drift are treated as first-class sources of surprise, which suits challenges where YAML on disk does not match what runs.
Under The Hood
The skill is instruction text only: the SKILL.md body, one reference checklist and a small agent config file that disables implicit invocation. It ships no scripts. The instructions tell the agent to inspect kube API objects, live describes and secret or config paths in the sandbox cluster the user supplies, which means the agent would run cluster commands itself. The skill replies in Simplified Chinese unless asked for English and runs only after the orchestrator skill is active.