kubernetes-secure

Generate Kubernetes manifests with default security hardening.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cassao29/claude-secure-plugins --skill kubernetes-secure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-secure
Source: https://github.com/cassao29/claude-secure-plugins/tree/main/plugins/devops/kubernetes-secure/skills/kubernetes-secure
Command: npx skills add https://github.com/cassao29/claude-secure-plugins --skill kubernetes-secure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps generate Kubernetes manifests that enforce security hardening by default, reducing misconfigurations and manual review time.

Core Features & Use Cases

  • Pod Security Context: Always include runAsNonRoot, runAsUser, and related securityContext settings.
  • Resource Limits: Define CPU/memory requests and limits for containers.
  • Network Policies: Include a default network policy to isolate pods.
  • Service & Probes: Prefer ClusterIP with health and readiness probes.
  • Secrets Management: Recommend or reference External Secrets rather than hardcoding secrets.

Quick Start

Use the kubernetes-secure skill to generate a Deployment manifest that:

  • runs containers with non-root user
  • specifies resource requests/limits
  • includes a network policy
  • uses a readiness and liveness probe

Frequently Asked Questions about kubernetes-secure

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

FAQPage Schema
How do I generate Kubernetes manifests with security hardening by default?

Security-hardened Kubernetes manifests embed pod security context (non-root user, explicit UIDs), resource limits, network policies, and image security controls automatically. This Skill generates complete manifests that enforce these defaults across Deployments and Pods without manual review.

What security context settings should I include in Kubernetes pod definitions?

Pod security context should enforce runAsNonRoot, specify runAsUser, and configure related restrictions like allowPrivilegeEscalation and readOnlyRootFilesystem. This Skill includes these settings in every generated manifest to reduce misconfigurations.

How do I enforce network isolation between Kubernetes pods?

NetworkPolicy resources isolate pods by default, restricting ingress and egress traffic. This Skill generates a default network policy alongside each Deployment to ensure pods communicate only with intended services.

Can I use this approach for managing secrets in Kubernetes deployments?

Yes. This Skill recommends or references External Secrets rather than hardcoding sensitive data, aligning with Kubernetes secret management best practices and reducing exposure risk in manifests.

Do I need resource limits and requests for container security in Kubernetes?

Yes. Defining CPU and memory requests and limits prevents resource exhaustion and enforces fair scheduling. This Skill embeds both in every container definition to harden deployments against denial-of-service scenarios.

What's the best way to configure health checks in secured Kubernetes deployments?

Include liveness and readiness probes to detect unhealthy containers and prevent traffic to failing instances. This Skill automatically adds probes to Deployments alongside security and resource configurations.