kubernetes-helm

Stars3

Forks1

UpdatedJuly 23, 2026 at 22:15

Kubernetes manifests, Helm charts, Kustomize, Argo CD, kubectl, helm, GitOps, or cluster rollout checks. Not for Docker-only files.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

ilude

ilude/dotfiles

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	kubernetes-helm
description	Kubernetes manifests, Helm charts, Kustomize, Argo CD, kubectl, helm, GitOps, or cluster rollout checks. Not for Docker-only files.

Kubernetes, Helm, and GitOps Workflow

Boundary

Use kubernetes-helm for cluster deployment contracts and GitOps validation. Use docker for image build and Compose-only work. Use terraform for cluster infrastructure provisioning.

Core Principles

Prefer immutable, Git-tracked image tags or digests. Avoid mutable latest style deployment inputs.
Treat branch, environment, namespace, and Argo CD application mapping as a contract. Do not change it casually or infer a new mapping from naming alone.
Keep reusable chart and manifest source separate from private values, kubeconfigs, sealed secrets source material, and tenant-specific credentials.

Validation Checklist

Run chart or manifest validation in CI or the same local commands CI uses.
Confirm the intended image identity: registry, repository, tag or digest, and build provenance from the deployment source.
Verify Argo CD sync status and health for the application when GitOps is in scope.
Check rollout status for changed workloads.
Inspect events for scheduling, image pull, probe, admission, or policy failures.
Check logs for changed pods or controllers before declaring the deployment healthy.

Quick Commands

Purpose	Commands
Render Helm	`helm template <release> <chart> -f <values>`
Lint Helm	`helm lint <chart>`
Diff rendered YAML	`kubectl diff -f <rendered.yaml>`
Rollout status	`kubectl rollout status deploy/<name> -n <namespace>`
Events	`kubectl get events -n <namespace> --sort-by=.lastTimestamp`
Logs	`kubectl logs -n <namespace> deploy/<name>`

Anti-patterns

Claiming success from CI alone when Argo CD sync, health, rollout, events, or logs were not checked.
Changing environment or branch mapping without updating the documented deployment contract.
Deploying mutable image tags in GitOps flows.
Mixing secret values into reusable chart defaults or examples.

More from this repository

same repository

pi-extension

ilude/dotfiles

Pi extensions and tool policy: extensions/*.ts, hooks, registerTool, promptGuidelines, registerCommand, footer/status UI, tool_result, session hooks, or subprocesses. Not for slash-command placement; use pi-command.

2026-08-023

docs

ilude/dotfiles

README, CHANGELOG, docs/, RFCs, ADRs, guides, or Markdown structure. Not for prose cleanup or archival work.

2026-07-273

no-ai-slop

ilude/dotfiles

Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.

2026-07-273

planning

ilude/dotfiles

Requirements, user stories, acceptance/verification criteria, or testable outcomes. Not for PRD drafting (/prd) or Pi /goal prompts.

2026-07-273

prd

ilude/dotfiles

Use for /prd-it or to draft, refine, or review a Product Requirements Document. Not for acceptance criteria, planning, or Pi /goal prompts.

2026-07-273

pi-log-analytics

ilude/dotfiles

Pi session, trace, metrics, routing, workflow-friction, workflow-telemetry, usage, or local JSONL analysis with DuckDB. Use for aggregating or correlating Pi runtime logs. Not for adding telemetry, generic SQL/database design, or non-Pi logs.

2026-07-273

Kubernetes, Helm, and GitOps Workflow

Boundary

Use kubernetes-helm for cluster deployment contracts and GitOps validation. Use docker for image build and Compose-only work. Use terraform for cluster infrastructure provisioning.

Core Principles

Prefer immutable, Git-tracked image tags or digests. Avoid mutable latest style deployment inputs.

Treat branch, environment, namespace, and Argo CD application mapping as a contract. Do not change it casually or infer a new mapping from naming alone.

Keep reusable chart and manifest source separate from private values, kubeconfigs, sealed secrets source material, and tenant-specific credentials.

Validation Checklist

Run chart or manifest validation in CI or the same local commands CI uses.

Confirm the intended image identity: registry, repository, tag or digest, and build provenance from the deployment source.

Verify Argo CD sync status and health for the application when GitOps is in scope.

Check rollout status for changed workloads.

Inspect events for scheduling, image pull, probe, admission, or policy failures.

Check logs for changed pods or controllers before declaring the deployment healthy.

Quick Commands

Purpose

Commands

Render Helm

helm template <release> <chart> -f <values>

Lint Helm

helm lint <chart>

Diff rendered YAML

kubectl diff -f <rendered.yaml>

Rollout status

kubectl rollout status deploy/<name> -n <namespace>

Events

kubectl get events -n <namespace> --sort-by=.lastTimestamp

Logs

kubectl logs -n <namespace> deploy/<name>

Anti-patterns

Claiming success from CI alone when Argo CD sync, health, rollout, events, or logs were not checked.

Changing environment or branch mapping without updating the documented deployment contract.

Deploying mutable image tags in GitOps flows.

Mixing secret values into reusable chart defaults or examples.