This message was deleted.

you have to redeploy the containers you can use like a:

kubectl rollout restart <namespace/deployment name>

to quickly redeploy using the latest tag. Generally using latest as image tag is not recommended.

@bulky-sunset-52084 I understand the kubectl command, but is there a way for rancher to do this automatically upon having a new image pushed to docker hub? I'm pretty sure that was available in 1.6

I don't believe for latest if you change the deployment manifest in some way rancher CD (fleet) will notice the change on the gitrepo and kubernetes will redeploy. But this is more on the container platform (docker/containerd) if k8s doesn't see a change on the manifest it wont ask the runtime to pull the latest image

Got it. I'll put something together that runs in the background and performs the redeploy. Thanks.