You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
The v8.2.1 tag of setup-snapshot-controller.yaml contains an old image (v8.2.0) instead of the expected v8.2.1.
also this container older csi-provisioner image v3.4.0, while csi-provisioner v5.2.0 is using snapshot-controller v8 version.
What you expected to happen:
Users relying on the v8.2.1 tag may unintentionally deploy an older snapshot-controller image (v8.2.0 instead of v8.2.1).
How to reproduce it:
Anything else we need to know?:
Environment:
Driver version:
Kubernetes version (use kubectl version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
What happened:
The v8.2.1 tag of setup-snapshot-controller.yaml contains an old image (v8.2.0) instead of the expected v8.2.1.
also this container older csi-provisioner image v3.4.0, while csi-provisioner v5.2.0 is using snapshot-controller v8 version.
What you expected to happen:
Users relying on the v8.2.1 tag may unintentionally deploy an older snapshot-controller image (v8.2.0 instead of v8.2.1).
How to reproduce it:
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: