Use authenticated pull for istio images #3082
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.
The test infra was pulling istio images from google container registry and at times the pull was failing because of registry issues. The fix is to use authenticated pulls from dockerhub, this should not hit the pull limit issue as seen with unauthenticated pulls.
The change from this PR creates a generic secret from file $HOME/.docker/config.json to use for pulling for the images.
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/10652/
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/10653/