Why do I see a MountingTargetFailed error for File Storage for VPC?
Virtual Private Cloud
Volume mounting fails with an error message similar to the following.
Warning FailedMount 68s kubelet MountVolume.SetUp failed for volume "pvc-c37fe511-ec6d-44c1-8c55-1b5e2c21ec5b" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Warning FailedMount 65s kubelet Unable to attach or mount volumes: unmounted volumes=[test-persistent-storage], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
New security group rules were introduced in cluster versions 4.11 and later. These rule changes mean that you must sync your security groups before you can use File Storage for VPC. For more information, see Adding File Storage for VPC to apps.
If your cluster was initially created at a version earlier than 4.11, make sure to sync your security groups by running the security group sync command.
-
Get the ID of the
kube-<clusterID>security group.ibmcloud is sg kube-<cluster-id> | grep ID -
Sync your security group settings.
ibmcloud ks security-group sync -c <cluster ID> --security-group <ID>
If your cluster was created at version 4.11 or later, verify that the node on whichever pod is deployed is allowlisted in the VNI security group.