[Bugfix for #5285] Expose flags for storage and untar images#5306
Conversation
43cef19 to
0982ab0
Compare
0982ab0 to
62f1907
Compare
|
Hi @camilamacedo86, thank you for the review! I've addressed all the documentation issues and replied concerning SHA usage. |
|
The |
…ar images Signed-off-by: Tatiana Krishtop <26544656+tkrishtop@users.noreply.github.com>
62f1907 to
b89a04a
Compare
|
New changes are detected. LGTM label has been removed. |
@jmrodri sorry for the issue, that was an uncommitted change for generated help text in |
|
Hi @estroz and @jmccormick2001, could you please approve CI runs? Everything should work now. |
|
Hi @jmccormick2001, thank you for re-running the tests! Yesterday's go/e2e tests were passing (the only problem was with the sanity tests), and today there is a timeout. |
Description of the change:
Exposes two tags to provide a possibility to overwrite hardcoded images:
Motivation for the change:
Closes #5285
Operator-sdk scorecard pulls two hardcoded images during the job execution:
operator-sdk/internal/scorecard/storage.go
Line 152 in 82e8ebb
operator-sdk/internal/scorecard/testpod.go
Line 36 in 50caa74
In the disconnected environment that pull doesn't work because the images are pinned by tags and not by digests.
As discussed in #5285 with @jmccormick2001 and @estroz , the solution could be to expose two tags to provide a possibility to overwrite these images with their local-registry copies.
Tests in disconnected environment
The changes from this PR were installed as operator-sdk-flag and tested by running in the disconnected environment
and
Here are scorecard logs of the above tests
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs