Fix cri-config-ensurer and registry images #23
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.
How to categorize this PR?
/area quality
/kind regression
/kind bug
What this PR does / why we need it:
Currently the cri-config-ensurer has the following code for the image:
gardener-extension-registry-cache/pkg/controller/criensurerdeployer.go
Line 134 in 0ef3e17
Note that it uses only the repository and ignores any tag.
This results in the Pod to be created such as:
After #17, the repo is switched to
eu.gcr.io/gardener-project/3rd/bash
and the latest tag does no longer exists. Hence, currently the cri-config-ensurer cannot be pulled at all:The same applies for the registry image:
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
N/A
Release note: