deploy: Fix csi-resizer tag and bump to v1.1.0 #1085
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.
Is this a bug fix or adding new feature?
Bug fix
What is this PR about? / Why do we need it?
Follow up on #1080. I tried to keep versions consistent between GCR and ECR, but did not notice 1.0.1 was not built against Kubernetes 1.18.3.
This uses
v1.1.0-eks-1-18-3
, so all ECR images are built against Kubernetes 1.18.3, and updates the GCR image as to v1.1.0 as well for consistency.Changelog: https://github.com/kubernetes-csi/external-resizer/blob/release-1.1/CHANGELOG-1.1.md
What testing is done?
Running the ECR image in multiple environments (actually
v1.1.0-eks-1-19-8
to be exact).