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
Anything else do we need to know:
The cluster.yml playbook executed successfully, but pods from ebs-csi-controller deployment were in CrashLoopBackOff status. The problem is with csi-snapshotter container:
# kubectl logs -n kube-system ebs-csi-controller-bd7fdfdd8-dqp84 csi-snapshotterflag provided but not defined: -connection-timeoutUsage of /csi-snapshotter:...
@floryut sure, but right now I am experiencing issues related to upgrade of csi-attacher (similar to #6358 (comment)). I will create a PR once the CSI driver is fully working.
Environment:
Kubespray version: 2.14.1
Anything else do we need to know:
The
cluster.yml
playbook executed successfully, but pods fromebs-csi-controller
deployment were inCrashLoopBackOff
status. The problem is withcsi-snapshotter
container:After some investigation I have found out that the
--connection-timeout
flag has been deprecated in release 1.1.0 of kubernetes-csi/external-snapshotter and removed in release 2.0.0. The version ofcsi-snapshotter
was updated from 1.2.0 to 2.1.1 in Kubespray 2.14.0. The flag does not exist in the newcsi-snapshotter
but remained in the Kubespray yamls https://github.com/kubernetes-sigs/kubespray/blob/v2.14.1/roles/kubernetes-apps/csi_driver/aws_ebs/templates/aws-ebs-csi-controllerservice.yml.j2#L92.The text was updated successfully, but these errors were encountered: