k8s-standards

Enforces security, labeling, and reliability standards when authoring Kubernetes manifests.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill k8s-standards-siegenthalerroger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-standards
Source: https://github.com/siegenthalerroger/.llmctl-marketplace/tree/main/plugins/llmctl-ops-0.2.1/skills/k8s-standards
Command: npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill k8s-standards-siegenthalerroger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Kubernetes manifests by hand often leads to insecure defaults, missing resource limits, inconsistent labels, and failed rollouts. This Skill provides a consistent set of configuration standards so every manifest you create or review follows security, reliability, and operational best practices. ## Core Features & Use Cases - Security Baseline: Enforces pod and container security contexts (runAsNonRoot, seccomp, dropped capabilities), least-privilege RBAC, NetworkPolicy, and pinned image tags. - Reliability Standards: Covers probes, resource requests/limits, QoS classes, HPA, Pod Disruption Budgets, and rolling update strategies. - Labeling and Review Checklist: Applies the standard app.kubernetes.io label scheme and provides a manifest review checklist for validation before apply. - Use Case: When writing a new Deployment for a service, invoke this Skill to generate a manifest with proper labels, security context, probes, and resource limits, then validate it with kubeconform before applying. ## Quick Start Ask the assistant to create a production-ready Kubernetes Deployment manifest for your service following the k8s standards.

Frequently Asked Questions about k8s-standards

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

FAQPage Schema
How do I write a secure Kubernetes Deployment manifest?▼

Set runAsNonRoot with an explicit runAsUser, use seccompProfile RuntimeDefault, disable allowPrivilegeEscalation, drop all capabilities, and use a read-only root filesystem. Also pin image tags and define resource requests and limits for every container.

What labels should Kubernetes resources use?▼

Use the recommended app.kubernetes.io label scheme: name, instance, version, component, part-of, and managed-by. Add workload context labels like environment or team, and use annotations for ownership and monitoring hints such as prometheus.io/scrape.

Does this apply to Helm charts and Kustomize overlays?▼

Yes, the standards apply to any Kubernetes YAML including Helm chart templates and Kustomize overlays. For Helm, validate rendered output by piping helm template output into kubeconform with the strict flag.

How do I validate Kubernetes manifests before applying them?▼

Run dry-run and schema validation with kubeconform in strict mode before applying. You can also use policy tools like OPA Conftest or Kyverno to enforce organizational policies on the manifests.

Why should I avoid using the latest image tag in Kubernetes?▼

The latest tag is mutable, so different nodes may run different image versions, making deployments non-reproducible and rollbacks unreliable. Pin images to specific immutable tags and integrate vulnerability scanning in CI/CD.