earlier, we used to update endpoint in value.yaml, same will be considered in csi-vast-node pod and related daemonset, and able to connect to vast server using PVC.
On latest version 2.42. in PVC we get an error,
Warning ProvisioningFailed 9m41s (x4 over 12m) csi.vastdata.com_-6443-4459-b655-15c5a809ba31 (combined from similar events): failed to provision volume with StorageClass "vast-filesystem": rpc error: code = Unknown desc = Exception calling application: Could not find endpoint.
field = endpoint
tip = Make sure endpoint is present in secret.
timestamp = 2024-10-14T06:56:16.680046
after adding endpoint in vast-filesystem secret, it started working.
in earlier versions, this change was not required. due to this upgrade from 2.3 to 2.4.2 fails additionally, need to add endpoint in secret.
Also, latest document is not updated that endpoint is required in vast-filesystem secret.
earlier, we used to update endpoint in value.yaml, same will be considered in csi-vast-node pod and related daemonset, and able to connect to vast server using PVC.
On latest version 2.42. in PVC we get an error,
Warning ProvisioningFailed 9m41s (x4 over 12m) csi.vastdata.com_-6443-4459-b655-15c5a809ba31 (combined from similar events): failed to provision volume with StorageClass "vast-filesystem": rpc error: code = Unknown desc = Exception calling application: Could not find endpoint.
field = endpoint
tip = Make sure endpoint is present in secret.
timestamp = 2024-10-14T06:56:16.680046
after adding endpoint in vast-filesystem secret, it started working.
in earlier versions, this change was not required. due to this upgrade from 2.3 to 2.4.2 fails additionally, need to add endpoint in secret.
Also, latest document is not updated that endpoint is required in vast-filesystem secret.