Bad webhook prevents restart of multiple deployments that use the same image #822
Description
If a flaky webhook is configured in the values yaml, and there are 2 deployments that use the same image, this is what happens:
- First deployment is updated
- Flaky webhook fails to send, returns 400
- Second deployment is not updated
Not sure if this is the correct behaviour, but I'd expect the deployments to be restarted regardless of the status of the webhook.