| name | k8s-release-verification |
| description | Verify Kubernetes release state for this MoruPark repository. Use when Codex needs to check `kubectl diff/apply` readiness, review post-deploy workload health, validate namespace and overlay consistency, inspect HPA, Deployment, or StatefulSet status, or diagnose rollout failures such as `ImagePullBackOff`, `CreateContainerConfigError`, probe errors, and image tag mismatches. |
K8s Release Verification
Use this skill when a Kubernetes deploy needs verification or rollout troubleshooting.
Quick Start
- Read references/release-checklist.md for the standard verification order.
- Read references/common-failures.md for recurring rollout failure patterns.
- Read
ssl.json when the request needs structured scene flow or grounded diagnostics.
Workflow
- Confirm the target environment and overlay path.
- Review whether the task is pre-apply validation, post-deploy verification, or failure diagnosis.
- Inspect namespace, image tag, Artifact Registry push state, and resource-kind consistency before mutation.
- Run the repo-standard post-deploy checks after apply.
- Verify the running workload images match the intended image tags and the latest successful Artifact Registry push for the deployed services.
- If Argo CD is expected for the environment, verify
Application sync health and confirm the cluster pulled the intended image tag; if Argo CD is absent, record that the deploy path is manual kubectl apply.
- If workloads are unhealthy, classify the failure as secret, image, probe, config, controller, or image-delivery mismatch.
- End with the smallest safe next action or the relevant owner handoff.
Guardrails
- Do not mutate Kubernetes resources without namespace or approved overlay context.
- Do not assume Redis is a Deployment in this repo; it is StatefulSet-based.
- Do not blame application code before ruling out secret sync, image pull, and probe configuration issues.
- Do not assume Argo CD auto-sync exists just because repo manifests are present; verify the CRD, Application, and sync status in-cluster.
- Do not skip post-deploy verification after a successful apply.
References
