EVEREST-107 update IMAGE_TAG_OWNER #589
Merged
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.
Problem:
After the 1.1.0 release it turned out that Everest still installs the everest-operator image from
perconalab
:Cause:
There is this make bundle command which is used during the operator release. This command uses
the IMG variable, which uses
the IMAGE_TAG_BASE variable, which uses
the IMAGE_TAG_OWNER variable, which was always set to
perconalab
and as a result config/manager/kustomization.yaml is always linked to
perconalab
Solution:
Update the Makefile during the release so that depending on the build type (RC or Release) the
IMAGE_TAG_OWNER
would point toperconalab
orpercona