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
{{ message }}
This repository was archived by the owner on Jul 22, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: workshop/Lab2/README.md
+1-17Lines changed: 1 addition & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,23 +67,7 @@ File sliver has an IOPS of 4GB and a max capacity of 12TB.
67
67
68
68
IBM Cloud File Storage provides fast access to your data for a cluster running in a single available zone. For higher availability, use a storage option that is designed for [geographically distributed data](https://cloud.ibm.com/docs/containers?topic=containers-storage_planning#persistent_storage_overview).
69
69
70
-
To create a `PersistentVolumeClaim` we must first get the availability zone of our cluster. Run the following commands to find out which region and availablility zone the worker nodes of your cluster are running in:
71
-
72
-
```
73
-
ibmcloud ks clusters [CLUSTER NAME]
74
-
ibmcloud ks workers -c [CLUSTER NAME]
75
-
```
76
-
77
-
Example output:
78
-
```
79
-
$ ibmcloud ks workers -c zaccone-guestbook2
80
-
81
-
OK
82
-
ID Public IP Private IP Flavor State Status Zone Version
83
-
kube-bun9o7vw0klq4okmgou0-zacconegues-default-0000010a 169.55.112.195 10.148.14.60 b3c.4x16.encrypted normal Ready wdc04 1.18.10_1532
84
-
```
85
-
86
-
Change the Review the yaml for the file storage `PersistentVolumeClaim`
70
+
Review the yaml for the file storage `PersistentVolumeClaim`. When we create this `PersistentVolumeClaim`, it automatically creates it within an availability zone where the worker nodes are located.
0 commit comments