Fix IMAGE_REPOSITORY in Prime upgrades #396
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Josh-Diamond
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Our 2.12 upgrades were failing the recent alphas. Upon looking in the logs, IMAGE_REPOSITORY appended a third
rancher, giving<registry>/rancher/rancher/rancher. This needs to be<registry/rancher/rancher. Locally testing a sanity upgrade from 2.12.4 -> 2.12.5-alpha2 and removing an extrarancherfixed this issue.While this is seen in 2.12, the reality is this issue will happen for any Prime release.