competition-k8s-control-plane

1# Competition K8s Control Plane
2 
3Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
4 
5Use this skill when the decisive path runs through Kubernetes control-plane state, API permissions, or controller behavior rather than a single container's runtime alone.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Separate manifest intent from live cluster state: API objects, mutations, controllers, secrets, and resulting workloads.
122. Identify the active principal first: service account, kubeconfig identity, node credential, webhook, or controller.
133. Map the smallest control-plane edge to its workload effect.
144. Keep RBAC, service accounts, owner references, namespace boundaries, and secret consumers in compact evidence blocks.
155. Reproduce the smallest cluster action that yields the decisive workload or secret effect.
16 
17## Workflow
18 
19### 1. Map The API Trust Path
20 
21- Record namespaces, service accounts, Roles, ClusterRoles, bindings, admission hooks, controllers, and the resources they can mutate.
22- Distinguish read access, create access, patch access, exec access, and secret access.
23- Keep principal, verb, resource, namespace, and resulting object in one chain.
24 
25### 2. Trace Mutation To Workload State
26…