[release-1.2] Fix gcr prow and github builds: cherry-pick of #1016, #1017, and #1020 #1064
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.
Is this a bug fix or adding new feature?
What is this PR about? / Why do we need it? #1062 just got merged which was a cherry-pick of #957.
I forgot that #957 on its own didn't work, it needed a few iterations of fixes: #1016, #1017, and #1020. Then after #1020 the builds passed: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/runs/3376750521, https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/aws-ebs-csi-driver-push-images/1428483776043814912
So of course, I need to cherry-pick these 3 PRs alongside 957. Whoops!
What testing is done?