Promote csi-attacher to v4.5.0 image and csi-provisioner to v4.0.0 image #6266
+2
−0
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.
Context:
Was dealing with the same issue for
node-driver-registrar
: kubernetes-csi/node-driver-registrar#359.Which was fixed by @cmontemuino on #6256 🚀
But this is not the only csi image that was not promoted.
My Change:
Promote the
csi-attacher
andcsi-provisioner
images as well.csi-provisioner image: https://console.cloud.google.com/gcr/images/k8s-staging-sig-storage/global/csi-provisioner
csi-attacher image: https://console.cloud.google.com/gcr/images/k8s-staging-sig-storage/global/csi-attacher