Move internal registry reference to scenario to avoid loosing abstraction in component #630
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 does this PR do?
Partially revert #602 and make some changes to be able to make existing scenari use the image built in the CI when pipeline ID and commit SHA are defined
Which scenarios this will impact?
docker, kind, eks
Motivation
Avoid loosing the abstraction on components. Components should not be coupled with Cloud Provider
Additional Notes