Skip to content

Commit 26c74d1

Browse files
Merge pull request #1816 from geremyCohen/ollama_image_update
Ollama image update
2 parents 5fa8432 + 229ca8f commit 26c74d1

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,11 @@ Arm CPUs are widely used in AI/ML workloads on Kubernetes. In this Learning Pat
1212

1313
First, you'll bring up an initial Kubernetes cluster with an amd64 node running an Ollama Deployment and Service (see **1: Initial Cluster (amd64)** in the image below).
1414

15-
Next, you'll expand the cluster by adding an arm64 deployment and service to it, forming a hybrid cluster (**2: Hybrid Cluster amd64/arm64**). This allows you to test both architectures together, and separately, to investigate performance.
15+
Next, you'll expand the cluster by adding an arm64 deployment and service to it, forming a hybrid cluster (**2: Hybrid Cluster (amd64/arm64)**). This allows you to test both architectures together, and separately, to investigate performance.
1616

17-
Once satisfied with arm64 performance, you can remove the amd64-specific node, deployment, and service, which then completes your migration to an arm64-only cluster (**3: Migrated Cluster (arm64)**.
17+
Once satisfied with arm64 performance, you can remove the amd64-specific node, deployment, and service, which then completes your migration to an arm64-only cluster (**3: Migration to arm64 complete**).
1818

19-
![Project Overview](images/general_flow.png)
19+
![Project Overview](images/general_flow_v2.png)
2020

2121
Once you've seen how easy it is to add arm64 nodes to an existing cluster, you will be ready to explore arm64 nodes for other workloads in your environment.
2222

64.3 KB
Loading

0 commit comments

Comments
 (0)