| name | artifact-registry-manual-rollout |
| description | Manually roll backend deployments in this MoruPark repository to a specific Artifact Registry image tag when Argo CD is not in use. Use when Codex needs to set `api-gateway`, `auth-service`, `goods-service`, or `queue-service` to a `sha-<8>` or other explicit tag, trigger Kubernetes to pull that image, and verify rollout completion in `morupark-prod`. |
Artifact Registry Manual Rollout
Use this skill when backend images were already pushed to Artifact Registry and the cluster must pull them without Argo CD.
Quick Start
- Confirm the target namespace and image tag.
- Verify the image path matches the prod registry project
yourssu-morupark-494902.
- Read the current deployment image before mutation.
- Use scripts/rollout-backend-image.ps1 once per owned service.
- Wait for rollout completion and verify the running deployment image matches the intended tag.
Workflow
- Identify which services need manual rollout.
- Resolve the exact image reference for each service using the prod Artifact Registry path.
- Verify the cluster is using the expected namespace and deployment names.
- For each target service, set the deployment container image to the explicit target tag.
- Wait for rollout completion before moving on to the next prod service unless the user explicitly wants concurrent rollouts.
- Verify the deployment spec and the newly created pods show the intended image tag.
- If rollout fails, classify whether the issue is image pull, scheduling, probe, secret, or config related.
Guardrails
- Do not use
latest when the goal is code-precise rollout verification; prefer sha-<8>.
- Do not assume Argo CD will reconcile manual image changes in this repository; verify the live deployment directly.
- Do not roll multiple prod backend services in parallel by default when the cluster is already resource-constrained.
- Do not mutate non-backend workloads through this skill.
References
