Kubernetes Skill
Kubernetes debugging, security hardening, and infrastructure tooling. Covers pod triage, RBAC, network policies, and cobaltcore hypervisor components.
Reference Loading Table
| Signal |
Reference |
Size |
| CrashLoopBackOff, OOMKilled, config error, health check, liveness probe, ImagePullBackOff, Pending, FailedScheduling |
references/crash-diagnosis.md |
~140 lines |
| service resolution, DNS, CoreDNS, port-forward, NetworkPolicy ingress/egress |
references/network-debugging.md |
~50 lines |
| CPU throttling, memory limit, OOMKill, ephemeral storage, DiskPressure, debug container |
references/resource-debugging.md |
~100 lines |
| RBAC, Role, RoleBinding, ClusterRole, ServiceAccount, least-privilege |
references/rbac-patterns.md |
~60 lines |
| PodSecurity, SecurityContext, runAsNonRoot, readOnlyRootFilesystem, restricted, baseline |
references/pod-security.md |
~90 lines |
| NetworkPolicy, default-deny, allow-list, namespace isolation |
references/network-policies.md |
~70 lines |
| cosign, Kyverno, OPA, admission controller, Sealed Secrets, External Secrets |
references/supply-chain.md |
~120 lines |
| kvm-exporter, metrics, prometheus, libvirt, hypervisor, collector, scrape, steal time, NUMA, cgroups, cloud hypervisor |
references/cobalt-kvm-exporter.md |
~800 lines |
| cobaltcore concurrency, goroutine, semaphore, TryLock |
references/cobalt-concurrency-patterns.md |
~200 lines |
| cobaltcore testing, mock, moq, Kind cluster |
references/cobalt-testing-patterns.md |
~200 lines |
| kubernetes debugging process, triage flow, diagnosis routing |
references/kubernetes-debugging.md |
~50 lines |
| kubernetes security process, RBAC + pod security + network hardening |
references/kubernetes-security.md |
~50 lines |
| cobaltcore overview, KVM exporter architecture, component identification |
references/cobalt-core.md |
~50 lines |
Loading rule. Read the references whose signals match the task before responding.
Phase 1: TRIAGE
Determine which Kubernetes domain the request targets:
| Domain |
Load references |
Action |
| Pod failure, CrashLoop, OOM |
crash-diagnosis, resource-debugging |
Triage flow |
| Network, DNS, service resolution |
network-debugging, network-policies |
Connectivity diagnosis |
| RBAC, permissions, roles |
rbac-patterns |
Access control |
| Pod hardening, container security |
pod-security |
Security posture |
| Image signing, secrets, admission |
supply-chain |
Supply chain |
| Cobaltcore / KVM exporter |
kvm-exporter + cobalt refs |
Component-specific |
Always specify -n <namespace> explicitly in every kubectl command.
Gate: Domain identified and relevant references loaded.
Phase 2: DIAGNOSE / RESPOND
For debugging: follow the triage flow — describe, logs, events, exec. Use read-only commands to gather evidence before proposing changes.
For security: provide concrete YAML manifests and specific configurations. Answer with reference-backed specifics, not generic advice.
For cobaltcore: use component-specific reference knowledge for architecture, metrics, configuration, and deployment details.
Gate: Specific, reference-backed diagnosis or response provided.
Phase 3: VERIFY
For debugging: confirm the fix resolves the symptom.
For security: validate against the misconfiguration table in supply-chain.md.
For cobaltcore: verify against component test patterns.
1---2name: kubernetes3description: Kubernetes operations: debugging, security, RBAC, and infrastructure tooling.4---56# Kubernetes Skill78Kubernetes debugging, security hardening, and infrastructure tooling. Covers pod triage, RBAC, network policies, and cobaltcore hypervisor components.910## Reference Loading Table1112| Signal | Reference | Size |13|--------|-----------|------|14| CrashLoopBackOff, OOMKilled, config error, health check, liveness probe, ImagePullBackOff, Pending, FailedScheduling | `references/crash-diagnosis.md` | ~140 lines |15| service resolution, DNS, CoreDNS, port-forward, NetworkPolicy ingress/egress | `references/network-debugging.md` | ~50 lines |16| CPU throttling, memory limit, OOMKill, ephemeral storage, DiskPressure, debug container | `references/resource-debugging.md` | ~100 lines |17| RBAC, Role, RoleBinding, ClusterRole, ServiceAccount, least-privilege | `references/rbac-patterns.md` | ~60 lines |18| PodSecurity, SecurityContext, runAsNonRoot, readOnlyRootFilesystem, restricted, baseline | `references/pod-security.md` | ~90 lines |19| NetworkPolicy, default-deny, allow-list, namespace isolation | `references/network-policies.md` | ~70 lines |20| cosign, Kyverno, OPA, admission controller, Sealed Secrets, External Secrets | `references/supply-chain.md` | ~120 lines |21| kvm-exporter, metrics, prometheus, libvirt, hypervisor, collector, scrape, steal time, NUMA, cgroups, cloud hypervisor | `references/cobalt-kvm-exporter.md` | ~800 lines |22| cobaltcore concurrency, goroutine, semaphore, TryLock | `references/cobalt-concurrency-patterns.md` | ~200 lines |23| cobaltcore testing, mock, moq, Kind cluster | `references/cobalt-testing-patterns.md` | ~200 lines |24| kubernetes debugging process, triage flow, diagnosis routing | `references/kubernetes-debugging.md` | ~50 lines |25| kubernetes security process, RBAC + pod security + network hardening | `references/kubernetes-security.md` | ~50 lines |26| cobaltcore overview, KVM exporter architecture, component identification | `references/cobalt-core.md` | ~50 lines |2728**Loading rule.** Read the references whose signals match the task before responding.2930---3132## Phase 1: TRIAGE3334Determine which Kubernetes domain the request targets:3536| Domain | Load references | Action |37|--------|----------------|--------|38| Pod failure, CrashLoop, OOM | crash-diagnosis, resource-debugging | Triage flow |39| Network, DNS, service resolution | network-debugging, network-policies | Connectivity diagnosis |40| RBAC, permissions, roles | rbac-patterns | Access control |41| Pod hardening, container security | pod-security | Security posture |42| Image signing, secrets, admission | supply-chain | Supply chain |43| Cobaltcore / KVM exporter | kvm-exporter + cobalt refs | Component-specific |4445Always specify `-n <namespace>` explicitly in every kubectl command.4647**Gate**: Domain identified and relevant references loaded.4849---5051## Phase 2: DIAGNOSE / RESPOND5253For debugging: follow the triage flow — describe, logs, events, exec. Use read-only commands to gather evidence before proposing changes.5455For security: provide concrete YAML manifests and specific configurations. Answer with reference-backed specifics, not generic advice.5657For cobaltcore: use component-specific reference knowledge for architecture, metrics, configuration, and deployment details.5859**Gate**: Specific, reference-backed diagnosis or response provided.6061---6263## Phase 3: VERIFY6465For debugging: confirm the fix resolves the symptom.66For security: validate against the misconfiguration table in supply-chain.md.67For cobaltcore: verify against component test patterns.
notque