When triggering the upgrade action, the created job ignores the version selected and uses the latest tag. This should be changed to use the correct tag for the management image.
Steps to reproduce
Try to upgrade env, running pods will have configuration based on latest dev code.
Detailed description
When triggering the upgrade action, the created job ignores the version selected and uses the latest tag. This should be changed to use the correct tag for the management image.
Steps to reproduce
Try to upgrade env, running pods will have configuration based on latest dev code.