Kubernetes Security Skill
Harden Kubernetes clusters and workloads through RBAC, pod security, network isolation, secret management, and supply chain controls.
Reference Loading Table
| Signal |
Reference |
Size |
| RBAC, Role, RoleBinding, ClusterRole, ServiceAccount, least-privilege, access control, permissions |
references/rbac-patterns.md |
~60 lines |
| PodSecurity, SecurityContext, runAsNonRoot, readOnlyRootFilesystem, restricted, baseline, image hardening, distroless, Dockerfile |
references/pod-security.md |
~90 lines |
| NetworkPolicy, default-deny, allow-list, egress, ingress, DNS, lateral movement, namespace isolation |
references/network-policies.md |
~70 lines |
| cosign, Kyverno, OPA, admission controller, Sealed Secrets, External Secrets, supply chain, misconfiguration, privileged |
references/supply-chain.md |
~120 lines |
Load greedily. If the user's question touches any signal keyword, load the matching reference before responding. Multiple signals matching = load all matching references.
Phase 1: IDENTIFY
Determine which security domain the user is asking about.
| Domain |
Reference |
| Access control, permissions, roles |
references/rbac-patterns.md |
| Pod hardening, container security |
references/pod-security.md |
| Network isolation, traffic rules |
references/network-policies.md |
| Image signing, secrets, admission control |
references/supply-chain.md |
If the question spans multiple domains, load all relevant references. Most production hardening tasks touch at least RBAC + pod security.
Gate: Domain identified. Reference(s) loaded. Proceed to Phase 2.
Phase 2: RESPOND
Use loaded reference knowledge to answer with concrete YAML manifests and specific configurations. The references contain complete, copy-paste-ready examples for each security domain.
For general Kubernetes debugging, pair with the kubernetes-debugging skill.
Gate: Question answered with reference-backed manifests, not generic advice.
Phase 3: VERIFY
Validate the security posture against the misconfiguration table in references/supply-chain.md. Flag any of the 8 common misconfigurations if present in the user's manifests.
References
1---2name: kubernetes-security3description: Kubernetes security: RBAC, PodSecurity, network policies.4---5
6# Kubernetes Security Skill
7
8Harden Kubernetes clusters and workloads through RBAC, pod security, network isolation, secret management, and supply chain controls.
9
10## Reference Loading Table
11
12| Signal | Reference | Size |
13|--------|-----------|------|
14| RBAC, Role, RoleBinding, ClusterRole, ServiceAccount, least-privilege, access control, permissions | `references/rbac-patterns.md` | ~60 lines |
15| PodSecurity, SecurityContext, runAsNonRoot, readOnlyRootFilesystem, restricted, baseline, image hardening, distroless, Dockerfile | `references/pod-security.md` | ~90 lines |
16| NetworkPolicy, default-deny, allow-list, egress, ingress, DNS, lateral movement, namespace isolation | `references/network-policies.md` | ~70 lines |
17| cosign, Kyverno, OPA, admission controller, Sealed Secrets, External Secrets, supply chain, misconfiguration, privileged | `references/supply-chain.md` | ~120 lines |
18
19**Load greedily.** If the user's question touches any signal keyword, load the matching reference before responding. Multiple signals matching = load all matching references.
20
21---
22
23## Phase 1: IDENTIFY
24
25Determine which security domain the user is asking about.
26
27| Domain | Reference |
28|--------|-----------|
29| Access control, permissions, roles | `references/rbac-patterns.md` |
30| Pod hardening, container security | `references/pod-security.md` |
31| Network isolation, traffic rules | `references/network-policies.md` |
32| Image signing, secrets, admission control | `references/supply-chain.md` |
33
34If the question spans multiple domains, load all relevant references. Most production hardening tasks touch at least RBAC + pod security.
35
36**Gate**: Domain identified. Reference(s) loaded. Proceed to Phase 2.
37
38---
39
40## Phase 2: RESPOND
41
42Use loaded reference knowledge to answer with concrete YAML manifests and specific configurations. The references contain complete, copy-paste-ready examples for each security domain.
43
44For general Kubernetes debugging, pair with the `kubernetes-debugging` skill.
45
46**Gate**: Question answered with reference-backed manifests, not generic advice.
47
48---
49
50## Phase 3: VERIFY
51
52Validate the security posture against the misconfiguration table in `references/supply-chain.md`. Flag any of the 8 common misconfigurations if present in the user's manifests.
53
54---
55
56## References
57
58- [Kubernetes Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/)
59- [Kubernetes Network Policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/)
60- [Kubernetes RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)
61- [External Secrets Operator](https://external-secrets.io/)
62- [Sealed Secrets](https://github.com/bitnami-labs/sealed-secrets)
63- [Cosign](https://docs.sigstore.dev/cosign/overview/)
64- [Kyverno](https://kyverno.io/)