Skip to content

Commit 79ee095

Browse files
Content rev
1 parent 61c4b67 commit 79ee095

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

content/learning-paths/servers-and-cloud-computing/multiarch_ollama_on_gke/0-spin_up_gke_cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Spin up the GKE Cluster
2+
title: Create the GKE Cluster
33
weight: 2
44

55
### FIXED, DO NOT MODIFY

content/learning-paths/servers-and-cloud-computing/multiarch_ollama_on_gke/2-deploy-arm64.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ To compare amd64 and arm64 performance, the c4a-standard-4 is used as the arm64
3333
8. Select *Create*
3434
9. After provisioning completes, select the newly created *arm64-pool* from the *Clusters* screen to take you to the *Node pool details* page.
3535

36-
Notice the taint below that GKE applies by default to the Arm node of `NoSchedule` if `arch=arm64`:
36+
Notice the default `NoSchedule` taint applied by GKE to Arm nodes with `arch=arm64`:
3737

3838
![arm node taint](images/taint_on_arm_node.png)
3939

@@ -174,9 +174,9 @@ When the pods show `Running` and the service shows a valid `External IP`, you ar
174174

175175
To test the service, use the previously created `model_util.sh` from the previous section.
176176

177-
Instead of the `amd64` parameter, replace it with `arm64`:
177+
Replace the `amd64` parameter with `arm64`:
178178

179-
3. Run the following to make an HTTP request to the amd64 ollama service on port 80:
179+
3. Run the following to make an HTTP request to the arm64 ollama service on port 80:
180180

181181
```bash
182182
./model_util.sh arm64 hello
@@ -194,6 +194,6 @@ Pod log output:
194194
[pod/ollama-arm64-deployment-678dc8556f-956d6/ollama-multiarch] 2025-03-25T21:25:21.547384356Z
195195
```
196196

197-
Once again, if you see "Ollama is running" then you have successfully setup your GKE cluster with both amd64 and arm64 nodes and pods running a deployment with the Ollama multi-architecture container.
197+
If you see the message "Ollama is running," you have successfully set up your GKE cluster with both amd64 and arm64 nodes, each running a deployment using the Ollama multi-architecture container.
198198

199199
Continue to the next section to analyze the performance.

content/learning-paths/servers-and-cloud-computing/multiarch_ollama_on_gke/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Migrate an amd64 cluster to a hybrid arm64 and amd64 cluster using a multi-architecture container image on GKE using Ollama
2+
title: Migrate an amd64 cluster to a hybrid arm64 and amd64 cluster using a multi-arch container image on GKE using Ollama
33

44
draft: true
55
cascade:

0 commit comments

Comments
 (0)