dev scriptworkers sometimes run stale versions of images

I sometimes notice that a dev version of a scriptworker will encounter errors that are not possible if they are running the expected version of the code. Sure enough, doing an additional deployment (with no added code changes) will fix the issue, which leads me to believe that there are circumstances that can cause us to be running outdated versions of images.

I've never seen this in production, so I'm suspicious that there's something different between the two either here, in cloudops-infra, or perhaps even in k8s-autoscale.

I've noticed this a couple of times this week, and @gabrielBusta reports that he's seen it as well.

Beginne damit, das Verhalten veralteter Images in einem dev-Deployment zu reproduzieren, und vergleiche die Image-Versionen vor und nach einer unveränderten erneuten Bereitstellung. Untersuche die Unterschiede bei den Deployments in scriptworker-scripts, cloudops-infra und k8s-autoscale. Als erledigt gilt die Aufgabe, wenn die Ursache der veralteten Images identifiziert ist und dev-Deployments konsistent die erwartete Codeversion ausführen.