chore(docker): Add major version tags to Docker images for easier updates #3200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds a
MAJOR_VERSION
tag (e.g.,v7
fromv7.12.0
) to the Docker images. The idea is that users can use a “major” tag to automatically get all minor/patch updates when they re-pull the image without pinning the full version.Motivation and Context
Many users want a stable image that updates with every minor/patch release in a major version. Adding
MAJOR_VERSION
tags makes it easy to track “stable” versions likev7
instead of always using exact versions likev7.12.0
. Such stable tags were also offered by the Bitnami images which are no longer available openly soon.This can be helpful especially when the images are used inside of larger units such as helm charts. This way the helm charts don't need to be updated every time to include patches of the oauth2-proxy images.
How Has This Been Tested?
Ran make locally and verified the commands invoked.
Checklist: