kubernetes gcp caching old image

Question

I'm running GKE cluster and there is a deployment that uses image which I push to Container Registry on GCP, issue is - even though I build the image and push it with latest tag, the deployment keeps on creating new pods with the old one cached - is there a way to update it without re-deploying (aka without destroying it first)?

There is a known issue with the kubernetes that even if you change configmaps the old config remains and you can either redeploy or workaround with

kubectl patch deployment $deployment -n $ns -p \
  "{\"spec\":{\"template\":{\"metadata\":{\"annotations\":{\"date\":\"`date +'%s'`\"}}}}}"

is there something similar with cached images?

By something similar you mean if there is something like kubectl patch deployment to update deployment image instead of deleting it and creating again from new yaml? — Jakub
yup exactly, same goes for resources limits/requests - once you create a deployment u cannot upgrade its resources unless re-deployed - I'm looking for the latter solution how to do it with commands - update image and update resources, if you know answer to any i'd appreciate it — CptDolphin

Jakub Jakub · Accepted Answer · 2020-02-07T13:51:49

I think you're looking for kubectl set or patch which I found there in kubernetes documentation.

To update image of deployment you can use kubectl set

kubectl set image deployment/name_of_deployment name_of_deployment=image:name_of_image

To update image of your pod you can use kubectl patch

kubectl patch pod name_of_pod  -p '{"spec":{"containers":[{"name":"name_of_pod_from_yaml","image":"name_of_image"}]}}'

You can always use kubectl edit to edit which allows you to directly edit any API resource you can retrieve via the command line tool.

kubectl edit deployment name_of_deployment

Let me know if you have any more questions.

kubernetes gcp caching old image

2 Answers