Menu

Individual skill

kubernetes-security

0upvotes

Harden Kubernetes clusters — RBAC, pod security, network policies, secrets, and control-plane protection.

skills/kubernetes-security/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Kubernetes orchestrates containers at scale — and its powerful defaults are insecure defaults: open dashboards, permissive RBAC, flat pod networking, and secrets in etcd. Securing Kubernetes means hardening the control plane, constraining workloads, segmenting the network, and governing the supply chain of what gets scheduled.

This skill covers the defensive hardening lifecycle: cluster configuration, workload policies, network segmentation, and continuous compliance checking.

Harden in layers from the outside in: control-plane and API access first (it is the keys to everything), then node security, then workload constraints, then network policy. A perfectly configured pod security policy means nothing if the API server is reachable with a stolen over-permissioned kubeconfig.

## When to use

- Provisioning or auditing a Kubernetes cluster (managed or self-hosted).
- Remediating benchmark findings (CIS Kubernetes Benchmark).
- Designing multi-tenant or multi-team cluster isolation.
- Implementing pod security, network policies, and admission control.
Back to top