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
The machine in my k8s cluster has two local ssd disks, which I mounted to /data1 and /data2 respectively. When I create storageClass, I hope that nodepath can be randomly selected from these two paths to balance a distribution of io as possible on the two disks. From the md, I see that nodePathMap is the place I can customize where to store the data on each node. So I wrote the yaml as:
I want to know if this way of writing can take effect when creating sc, so that the nodepath of sc can be randomly selected from these two paths of each node in the cluster.
The text was updated successfully, but these errors were encountered:
The machine in my k8s cluster has two local ssd disks, which I mounted to /data1 and /data2 respectively. When I create storageClass, I hope that nodepath can be randomly selected from these two paths to balance a distribution of io as possible on the two disks. From the md, I see that nodePathMap is the place I can customize where to store the data on each node. So I wrote the yaml as:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: local-path-data3
provisioner: rancher.io/local-path
parameters:
nodePathMap: [
{
"node": "DEFAULT_PATH_FOR_NON_LISTED_NODES",
"paths": ["/data1", "/data2"]
}
]
volumeBindingMode: WaitForFirstConsumer
reclaimPolicy: Delete
I want to know if this way of writing can take effect when creating sc, so that the nodepath of sc can be randomly selected from these two paths of each node in the cluster.
The text was updated successfully, but these errors were encountered: