Skip to content

zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-k8s-control-plane

competition-k8s-control-plane

Verified

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kubernetes API analysis, service-account trust, RBAC edges, admission and controller behavior, cluster secrets, workload mutation, and namespace-scoped drift. Use when the user asks to inspect kube API permissions, service-account tokens, RoleBinding or ClusterRoleBinding edges, admission webhooks, controller-created pods, secret exposure, or why live workloads differ from manifests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

FileKindSize
SKILL.mdskill md3.4 KB
agents/openai.yamlconfig404 B
references/k8s-control-plane.mdmarkdown1.1 KB

references/k8s-control-plane.md

View on GitHub
# K8s Control Plane Checklist

## First Pass

- Namespaces, service accounts, kubeconfigs, tokens, Roles, ClusterRoles, bindings
- Admission webhooks, mutating or validating policy, controllers, operators, CRDs
- Secrets, ConfigMaps, projected volumes, generated Jobs, and owner references

## Trust Chain To Reconstruct

1. Principal or token identified
2. RBAC or admission edge established
3. Object create, patch, or read action performed
4. Controller or scheduler turns object into workload state
5. Secret, route, workload, or artifact effect observed

## Evidence To Keep Together

- Principal side: service account, token source, namespace, binding, verb, resource
- Mutation side: object manifest, admission change, controller output, owner refs
- Effect side: mounted secret, env var, spawned pod, reachable route, or recovered artifact

## Common Pitfalls

- Stopping at a RoleBinding without proving the resulting API action
- Explaining pod behavior without showing which cluster object created it
- Mixing static YAML and live cluster objects without accounting for admission or controller drift
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall