You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Image Automation and defined an image policy to track a specific version of our app. To rollout a breaking configuration change, the new image is tagged with a new major version, so it is not included in the semver range of the image policy. Then we update the deployment config, image version tag and image policy semver range in the same commit and push it to our infrastructure git repo.
At first this works fine, however shortly after the new version is deployed, flux makes an image update and downgrades to the old image version which is not included in the semver range of the image policy anymore! This breaks our application, because the old image does not work with the new deployment configuration. After some time flux updates the image again to the new image version.
How can we ensure flux does not downgrade our image versions during critical updates with configuration changes?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We use Image Automation and defined an image policy to track a specific version of our app. To rollout a breaking configuration change, the new image is tagged with a new major version, so it is not included in the semver range of the image policy. Then we update the deployment config, image version tag and image policy semver range in the same commit and push it to our infrastructure git repo.
At first this works fine, however shortly after the new version is deployed, flux makes an image update and downgrades to the old image version which is not included in the semver range of the image policy anymore! This breaks our application, because the old image does not work with the new deployment configuration. After some time flux updates the image again to the new image version.
How can we ensure flux does not downgrade our image versions during critical updates with configuration changes?
Beta Was this translation helpful? Give feedback.
All reactions