Restart task-runner during deploy in CI
Our task runner often uses an outdated image in dev, as there is nothing day-to-day, to cause the pod to be restarted, (even though a new task-runner latest image is created at least nightly). This isn't a problem in a production environment, because the images are tagged with versions, and the version change is enough to cause restarts when needed.
But in CI, the lack of restarts means that our task-runner is often outdated, vs the code that is running in unicorn and sidekiq (which are being updated by our operator).
This causes issues in our backup tests, as the task-runner is used for the backup restore.
We should add a step to the end of our CI's deploy, to force the task-runner to restart on each deploy.