k8s-security-policies

Implement Kubernetes security policies for network isolation, pod hardening, and least-privilege access.

Updated May 16, 2026
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill k8s-security-policies-p-o-ke-nae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-security-policies
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/k8s-security-policies
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill k8s-security-policies-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you secure Kubernetes clusters by turning broad, error-prone access into explicit network, pod, and identity controls for production environments.

Core Features & Use Cases

  • Network Isolation: Define default-deny and allowlist NetworkPolicy rules for service-to-service traffic, DNS, ingress controllers, databases, and cross-namespace access.
  • Pod Hardening: Apply Pod Security Standards and secure container settings such as non-root execution, read-only filesystems, seccomp, and dropped capabilities.
  • Least-Privilege Access: Build Roles, ClusterRoles, and RoleBindings that limit permissions for users, service accounts, and CI/CD workflows.
  • Policy Enforcement: Extend safeguards with OPA Gatekeeper and Istio authorization and mTLS policies for multi-layer cluster protection.

Quick Start

Ask the skill to generate secure Kubernetes policies for a production namespace with default-deny networking, restricted pod settings, and least-privilege RBAC.

Frequently Asked Questions about k8s-security-policies

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

FAQPage Schema
How do I configure Kubernetes NetworkPolicy for default-deny and namespace isolation?

Kubernetes NetworkPolicy default-deny rules block all ingress and egress traffic, then allowlist specific service-to-service, DNS, ingress, and cross-namespace access for multi-tenant isolation. You define explicit allow rules to secure service communication.

What Kubernetes pod security settings are needed for production hardening?

Pod hardening for production clusters requires applying Pod Security Standards with non-root execution, read-only filesystems, seccomp profiles, and dropped Linux capabilities to restrict container privileges and prevent escalation.

How do I set up least-privilege RBAC roles for Kubernetes service accounts?

Least-privilege RBAC limits permissions by creating targeted Roles and ClusterRoles bound via RoleBindings to specific users, service accounts, and CI/CD workflows, ensuring components only access the resources they explicitly need.

Can I use OPA Gatekeeper and Istio together for Kubernetes admission control?

OPA Gatekeeper and Istio can be combined for multi-layer cluster protection. Gatekeeper handles admission control for resource creation, while Istio enforces service mesh mTLS and authorization policies for runtime traffic security.

Does this approach work for multi-tenant Kubernetes cluster isolation?

Yes, multi-tenant isolation is achieved by combining namespace-level Pod Security Standards enforcement, default-deny NetworkPolicy design, and least-privilege RBAC patterning to restrict cross-tenant access and secure shared cluster environments.