k8s-security-policies

Define and implement Kubernetes NetworkPolicy, Pod Security Standards, and RBAC across namespaces.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill k8s-security-policies-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-security-policies
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/k8s-security-policies
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill k8s-security-policies-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Kubernetes deployments often lack consistent security controls, leading to misconfigurations and exposure. This Skill provides a structured approach to implementing network isolation, pod security standards, and least-privilege RBAC across clusters.

Core Features & Use Cases

  • Network isolation: Define and apply NetworkPolicy across namespaces to limit traffic between pods.
  • Pod security standards: Enforce baseline, restricted, or privileged profiles to control pod capabilities and runtime permissions.
  • Least-privilege RBAC: Configure Role/ClusterRole and bindings to follow the principle of least privilege and support admission controls.
  • Templates and references: Reuse network policy templates and RBAC patterns for quick, compliant deployments.
  • Use Case: Secure a multi-tenant cluster by isolating workloads and restricting cross-namespace access.

Quick Start

Apply the provided network policy, Pod Security Standards, and RBAC templates to your Kubernetes namespaces to harden cluster security.

Frequently Asked Questions about k8s-security-policies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Kubernetes network policies to isolate workloads across namespaces?

Kubernetes network policies isolate workloads by limiting traffic between pods across namespaces. You apply NetworkPolicy YAML manifests to your namespaces to enforce network isolation and restrict cross-namespace access in multi-tenant clusters.

How do I configure least privilege RBAC for Kubernetes namespaces?

Least privilege RBAC in Kubernetes is configured by applying Role and ClusterRole bindings to namespaces. You use reusable RBAC templates to restrict permissions and support admission controls for compliant deployments.

What is the best way to secure a multi-tenant Kubernetes cluster?

Securing a multi-tenant Kubernetes cluster requires applying network isolation, pod security standards, and least-privilege RBAC across namespaces. You use structured YAML templates and reference materials to isolate workloads and restrict cross-namespace access.

Can I reuse Kubernetes security policy templates for multiple deployments?

Yes, you can reuse Kubernetes security policy templates for multiple deployments. The Skill provides reusable network policy templates and RBAC patterns designed for quick, compliant deployments across production-grade clusters.

When do I need to apply Pod Security Standards in Kubernetes?

You need to apply Pod Security Standards in Kubernetes when you want to enforce baseline, restricted, or privileged profiles to control pod capabilities. This prevents misconfigurations and secures runtime permissions across your cluster namespaces.