File tree Expand file tree Collapse file tree 1 file changed +17
-1
lines changed Expand file tree Collapse file tree 1 file changed +17
-1
lines changed Original file line number Diff line number Diff line change 73
73
kubectl -n peerprep get all
74
74
```
75
75
76
- You should be able to see the Horizontal Pod AutoScaler scaling up the services in respond to
76
+ You should be able to see the Horizontal Pod AutoScaler scaling up the services in respond to
77
77
resource demand.
78
78
79
79
3. Run <kbd>Ctrl</kbd>+<kbd>C</kbd> to interrupt and
185
185
--num-nodes 1 \
186
186
--min-nodes 1 \
187
187
--max-nodes 25 \
188
+ --disk-size 20 \
188
189
--region=asia-southeast1-c
189
190
```
190
191
192
+ - We configure the node pool using the above command to create a cluster with
193
+ a node pool having the following characteristics:
194
+ - Preemptible: To schedule cheaper pods that can be claimed back by GCloud to save
195
+ costs
196
+ - Machine Type: `e2-small`
197
+ - This provides a good balance between performance and cost.
198
+ - Autoscaling: This allows the node pool to resize automatically, allowing us
199
+ to scale our deployments without manually managing nodes
200
+ - Num Nodes (Initial Number of Nodes): 1. We let the cluster operate first, and scale
201
+ up if needed.
202
+ - Min Nodes: 1. This ensures our cluster is always up.
203
+ - Max Nodes: 25. This prevents our cluster from scaling too large.
204
+ - Disk Size: 20GB. This prevents our cluster from requesting more than the Google Cloud
205
+ quota of 500GB SSD, as the default is 100GB per node.
206
+
191
207
5. Once the cluster has been created, run the commands below to configure `kubectl` and connect to the cluster:
192
208
193
209
```sh
You can’t perform that action at this time.
0 commit comments