Actual Behavior
hello I created an pvc, and it auto created an pv which bound to this pvc
then I check the pv config it has Path:
/var/lib/rancher/k3s/storage/pvc-53553bbf-8198-4096-bd78-2c78ff4c5b1c_argo_output
but where this path is located? I using windows with wsl,
the path looks like an linux folder, but after using wsl -d rancher-desktop to check,couldn't find above folder
PS C:\WINDOWS\system32> .\kubectl.exe -nargo get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-53553bbf-8198-4096-bd78-2c78ff4c5b1c 5Gi RWO Delete Bound argo/output local-path 7d1h
pvc-66258aa0-c95d-4dc9-b1f7-fe22980046fe 1Gi RWO Delete Bound argo/input local-path 7d1h
PS C:\WINDOWS\system32> .\kubectl.exe -nargo get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
output Bound pvc-53553bbf-8198-4096-bd78-2c78ff4c5b1c 5Gi RWO local-path 7d1h
input Bound pvc-66258aa0-c95d-4dc9-b1f7-fe22980046fe 1Gi RWO local-path 7d1h
Steps to Reproduce
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
pv.kubernetes.io/bind-completed: "yes"
pv.kubernetes.io/bound-by-controller: "yes"
volume.beta.kubernetes.io/storage-provisioner: rancher.io/local-path
volume.kubernetes.io/selected-node: hicdn198
volume.kubernetes.io/storage-provisioner: rancher.io/local-path
creationTimestamp: "2022-05-20T06:17:15Z"
finalizers:
- kubernetes.io/pvc-protection
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:spec:
f:accessModes: {}
f:resources:
f:requests:
.: {}
f:storage: {}
f:storageClassName: {}
f:volumeMode: {}
manager: steve.exe
operation: Update
time: "2022-05-20T06:17:15Z"
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:pv.kubernetes.io/bind-completed: {}
f:pv.kubernetes.io/bound-by-controller: {}
f:volume.beta.kubernetes.io/storage-provisioner: {}
f:volume.kubernetes.io/selected-node: {}
f:volume.kubernetes.io/storage-provisioner: {}
f:spec:
f:volumeName: {}
manager: k3s
operation: Update
time: "2022-05-20T06:18:31Z"
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:status:
f:accessModes: {}
f:capacity:
.: {}
f:storage: {}
f:phase: {}
manager: k3s
operation: Update
subresource: status
time: "2022-05-20T06:18:31Z"
name: input
namespace: argo
resourceVersion: "144299"
uid: 66258aa0-c95d-4dc9-b1f7-fe22980046fe
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: local-path
volumeMode: Filesystem
volumeName: pvc-66258aa0-c95d-4dc9-b1f7-fe22980046fe
status:
accessModes:
- ReadWriteOnce
capacity:
storage: 1Gi
phase: Bound
Result
no pv folder found
Expected Behavior
should be an pv folder
Additional Information
No response
Rancher Desktop Version
1.3.0
Rancher Desktop K8s Version
k3s 1.23.5
Which container runtime are you using?
containerd (nerdctl)
What operating system are you using?
Windows
Operating System / Build Version
win11
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
No response
Actual Behavior
hello I created an pvc, and it auto created an pv which bound to this pvc
then I check the pv config it has Path:
/var/lib/rancher/k3s/storage/pvc-53553bbf-8198-4096-bd78-2c78ff4c5b1c_argo_output
but where this path is located? I using windows with wsl,
the path looks like an linux folder, but after using wsl -d rancher-desktop to check,couldn't find above folder
Steps to Reproduce
Result
no pv folder found
Expected Behavior
should be an pv folder
Additional Information
No response
Rancher Desktop Version
1.3.0
Rancher Desktop K8s Version
k3s 1.23.5
Which container runtime are you using?
containerd (nerdctl)
What operating system are you using?
Windows
Operating System / Build Version
win11
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
No response