メニュー
Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | kubernetes-deployment |
| description | Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations. |
| category | granular-workflow-bundle |
| risk | safe |
| source | personal |
| date_added | 2026-02-27 |
Specialized workflow for deploying applications to Kubernetes including container orchestration, Helm charts, service mesh configuration, and production-ready K8s patterns.
Use this workflow when:
docker-expert - Docker containerizationk8s-manifest-generator - K8s manifestsUse @docker-expert to containerize application for K8s
k8s-manifest-generator - Manifest generationkubernetes-architect - K8s architectureUse @k8s-manifest-generator to create K8s manifests
helm-chart-scaffolding - Helm chartsUse @helm-chart-scaffolding to create Helm chart
istio-traffic-management - Istiolinkerd-patterns - Linkerdservice-mesh-expert - Service meshUse @istio-traffic-management to configure Istio
k8s-security-policies - K8s securitymtls-configuration - mTLSUse @k8s-security-policies to secure Kubernetes cluster
grafana-dashboards - Grafanaprometheus-configuration - PrometheusUse @prometheus-configuration to set up K8s monitoring
deployment-engineer - Deploymentgitops-workflow - GitOpsUse @gitops-workflow to implement GitOps deployment
cloud-devops - Cloud/DevOpsterraform-infrastructure - Infrastructuredocker-containerization - ContainersDiagnose a broken/slow/crashlooping app in kubenuc or k8s-vms-daniele — gather evidence via Graylog/Grafana/kubectl before asking the user anything. Triggers on "X is down", "X is crashlooping", "X is erroring", "X is slow", "why did X restart".
Route documentation/notes to the right destination (Confluence, README/CLAUDE.md, Obsidian, or NetBox) based on content type, and confirm the exact destination with the user before writing anything. Also invoke proactively — before opening a PR — when the change is a new operational gotcha, an incident, a security-hardening trade-off, a version-pin rationale, a new app/cluster, or a structural Terraform/infra change, to decide whether README.md, a CLAUDE.md, or Confluence needs updating.
Cluster lifecycle operations — setting up new clusters, kubenuc-test overlay pattern, kustomize patch conventions, and FluxCD bootstrap structure for infra-cd clusters.
Before adding any new Prometheus scrape target or exporter, check the active-series budget in Grafana Cloud and propose write_relabel drops if needed. Triggers on "add a scrape config", "add an exporter", "enable metrics for X", "add a ServiceMonitor". Gates any change that could grow active series count.
Review a Renovate PR before merging — read the changelog, diff values against this repo's overrides, check e2e status, flag major bumps, and produce a merge checklist. Triggers on "review this renovate PR", "should I merge this chart bump", "is this renovate PR safe".
Ansible playbook/role conventions, Molecule testing patterns, and ansible-agent invocation for the infra-cd repository.