Fix gcr prow build failing because of IMAGE variable collision #1017
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?
build is failing. It seems like the build container already sets IMAGE to gcr.io/k8s-testimages/gcb-docker-gcloud:v20200421-a2bf5f8 so the new Makefile rule tries pushing to this invalid tag: "invalid tag "gcr.io/k8s-testimages/gcb-docker-gcloud:v20200421-a2bf5f8:v20210805-helm-chart-aws-ebs-csi-driver-2.0.4-3-gf30d7f8e-linux-amd64-amazon": invalid reference format". The fix should be to override IMAGE for the
make
call. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/aws-ebs-csi-driver-push-images/1423392293334814720What testing is done?
Can't verify locally, will check if build succeeds in master branch after this merges.