BUGFIX: identity mapping with EXACT and REPLACE is ignored #104
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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
I had problems with Istio, because it creates an ingress POD which has a dummy image with name "auto" (see here ).
Imageswap interpreted this as "docker.io/auto" and replaced it according to my rules with "dockermirror.example.com/auto".
This caused problems.
To avoid this I added the following rule to the mappings:
This should fix the problem, but it does not.
In the logfile I can see, that the exact mapping was found, but nevertheless furter mappings like (docker.io->dockermirror.example.com) were applied.
Which issue(s) this PR fixes:
Fixes #
did not create an issue for this PR
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., usage docs, etc.: