skills.rest
vonomarap
vonomarapCOMMUNITY
Explore all skills by this author →
GitHub

kubernetes-specialist

Generate declarative Kubernetes YAML manifests and Helm chart templates.

Updated Aug 30, 2025
Search Tags:#rbac#kubernetes#manifests#helm#gitops#service-mesh#networkpolicy
One-click install
npx skills add https://github.com/vonomarap/kanokna --skill kubernetes-specialist-vonomarap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubernetes-specialist
Source: https://github.com/vonomarap/kanokna/tree/main/.agents/skills/kubernetes-specialist
Command: npx skills add https://github.com/vonomarap/kanokna --skill kubernetes-specialist-vonomarap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deploying and operating production Kubernetes workloads is complex and error-prone; this Skill reduces risk and time-to-deploy by providing repeatable, secure, and observable manifests and guidance tailored for production clusters. It codifies best practices for resource sizing, health checks, least-privilege access, network segmentation, and storage so teams avoid common outages and security gaps.

Core Features & Use Cases

  • Manifest Design: Generate declarative YAML for Deployments, StatefulSets, DaemonSets, CronJobs and Jobs with requests/limits, probes, and sensible defaults.
  • Security & Policies: Create RBAC, NetworkPolicy, PodSecurity/PSS guidance and least-privilege ServiceAccounts and RoleBindings.
  • Packaging & Delivery: Produce Helm chart structure, values.yaml recommendations, and GitOps-ready overlays for ArgoCD/Flux.
  • Storage & Scaling: Recommend StorageClasses, PVC patterns, HPA/VPA and namespace quotas for cost and availability.
  • Troubleshooting: Provide kubectl debugging steps, diagnostics, and remediation patterns for common pod, scheduling, and networking failures.

Quick Start

Create production-ready Kubernetes YAML and a Helm chart for a web application including resource requests/limits, liveness/readiness probes, namespace isolation, RBAC, and a NetworkPolicy.

Frequently Asked Questions about kubernetes-specialist

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

FAQPage Schema
How do I generate production-grade Kubernetes manifests with resource requests, limits, and liveness probes?▼

To create production-grade Kubernetes manifests, define declarative YAML for Deployments and StatefulSets with resource requests, limits, and liveness or readiness probes that ensure workload availability and prevent resource exhaustion in production clusters.

What is the best way to configure RBAC and NetworkPolicy for namespace isolation in Kubernetes?▼

Configure RBAC and NetworkPolicy for namespace isolation by creating least-privilege ServiceAccounts, Roles, RoleBindings, and network segmentation rules that restrict pod communication, codifying security best practices to prevent unauthorized access and lateral movement.

How do I structure Helm charts and GitOps overlays for ArgoCD or Flux delivery?▼

Structure Helm charts and GitOps overlays by producing Helm chart templates, values.yaml recommendations, and ArgoCD or Flux-ready configurations that automate CI/CD delivery of declarative Kubernetes manifests with sensible defaults and environment-specific parameterization.

Can I use this approach to set up persistent storage and StorageClasses for scalable workloads?▼

Yes, you can set up persistent storage and StorageClasses for scalable workloads by recommending PVC patterns, StorageClasses, HPA, VPA, and namespace quotas that optimize cost and availability for stateful applications running in production Kubernetes clusters.

Does this cover troubleshooting and debugging for Kubernetes pod scheduling and control-plane failures?▼

Yes, this covers Kubernetes troubleshooting by providing kubectl debugging steps, diagnostics, and remediation patterns for common pod scheduling, networking, and control-plane failures to quickly identify and resolve cluster issues.

When do I need least-privilege RBAC rules and PodSecurity standards for automated CI/CD delivery?▼

You need least-privilege RBAC rules and PodSecurity standards for automated CI/CD delivery when deploying production workloads to enforce security, restrict service account permissions, and ensure declarative manifests meet compliance requirements before reaching the cluster.

Related Skills

Explore More Software Engineering Skills→
andisabandisab

helm-charts

Develop and manage Helm charts for Kubernetes applications.

Community
Advanced
EstomEstom

kubernetes-specialist

Generate production-grade Kubernetes YAML manifests with security hardening guidance.

Community
Advanced
nksethnkseth

devops-engineer

Automate CI/CD pipelines, containerization, and infrastructure-as-code workflows.

Community
Advanced
igpastorigpastor

Infrastructure as Code Skill

Generate Terraform, Kubernetes, Helm, CloudFormation, and Docker Compose configurations for cloud resources.

Community
Advanced