Digest-Pinned GitOps Image Promotion with ArgoCD on GKEDigest-Pinned GitOps Image Promotion with ArgoCD on GKE
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Making production deploys boring: digest-pinned image promotion with ArgoCD
At a healthcare data company running on GKE, moving releases from staging to production was manual and easy to get wrong. People retagged images by hand, so what passed in staging wasn’t always exactly what ran in production.
I replaced that with a GitOps promotion flow built on ArgoCD Image Updater, covering about 30 services across staging and production. Staging tracks new builds automatically, and Git records the exact image digest for each service. A promotion script reads those pinned digests and promotes the same images to production, so production runs the identical artifact that was tested, with an audit trail in Git. That matters in a SOC2/HITRUST environment.
A Workload Identity lesson from the rollout: if pods get 403s minting tokens even though the service account looks correct, check two metadata endpoints. /email only shows the annotation. /token tests whether impersonation is actually authorized. In our case the Kubernetes service account name didn’t exactly match the IAM binding, and that pair of checks found it in minutes.
Stack: GKE, ArgoCD + Image Updater, Helm, Artifact Registry, Workload Identity, Python.
I help small teams set up reliable GCP platforms: GitOps CD, Terraform, Kubernetes and observability. If your deploys are still manual or fragile, I’m happy to talk.
— Jonah, Keelwork
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started