Commit f42440cc authored by Kubernetes Submit Queue's avatar Kubernetes Submit Queue Committed by GitHub

Merge pull request #39523 from xiangfeiz/fixVsphereVolumeExample

Automatic merge from submit-queue (batch tested with PRs 40215, 40340, 39523) Use the same name in volumeMounts and volumes In some example files of vSphere volumes, volumeMounts and volumes have different names. kubectl create will fail with error message saying the pod is invalid because volumeMount with the name is not found. **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note ```
parents f9b3e739 eeae1bed
...@@ -176,7 +176,7 @@ ...@@ -176,7 +176,7 @@
- name: test-volume - name: test-volume
mountPath: /test-vmdk mountPath: /test-vmdk
volumes: volumes:
- name: vmdk-storage - name: test-volume
persistentVolumeClaim: persistentVolumeClaim:
claimName: pvc0001 claimName: pvc0001
``` ```
...@@ -315,7 +315,7 @@ ...@@ -315,7 +315,7 @@
- name: test-volume - name: test-volume
mountPath: /test-vmdk mountPath: /test-vmdk
volumes: volumes:
- name: vmdk-storage - name: test-volume
persistentVolumeClaim: persistentVolumeClaim:
claimName: pvcsc001 claimName: pvcsc001
``` ```
......
...@@ -10,6 +10,6 @@ spec: ...@@ -10,6 +10,6 @@ spec:
- name: test-volume - name: test-volume
mountPath: /test-vmdk mountPath: /test-vmdk
volumes: volumes:
- name: vmdk-storage - name: test-volume
persistentVolumeClaim: persistentVolumeClaim:
claimName: pvc0001 claimName: pvc0001
\ No newline at end of file
...@@ -10,6 +10,6 @@ spec: ...@@ -10,6 +10,6 @@ spec:
- name: test-volume - name: test-volume
mountPath: /test-vmdk mountPath: /test-vmdk
volumes: volumes:
- name: vmdk-storage - name: test-volume
persistentVolumeClaim: persistentVolumeClaim:
claimName: pvcsc0001 claimName: pvcsc001
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment