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
Copy file name to clipboardExpand all lines: content/blog/getting-started-with-volume-snapshots-on-a-kubernetes-cluster-in-hpe-greenlake-for-private-cloud-enterprise.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -631,7 +631,7 @@ Here is the PVC YAML manifest file that creates a new PVC *mysql-pvc-restore* fr
631
631
632
632
633
633
634
-
```markdown
634
+
```shell
635
635
$ cat mysql-pvc-restore.yaml
636
636
apiVersion: v1
637
637
kind: PersistentVolumeClaim
@@ -665,15 +665,14 @@ You will see the new PVC *mysql-pvc-restore*, together with its PV, is crated
665
665
666
666
667
667
668
-
```markdown
668
+
```shell
669
669
$ kubectl get persistentvolumeclaims -n mysql
670
670
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
0 commit comments