Skip to content

Commit 6acf3c0

Browse files
committed
Enhance AKS cluster deployment guide with multi-architecture benefits and improved clarity
1 parent f232560 commit 6acf3c0

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

content/learning-paths/servers-and-cloud-computing/multiarch_nginx_on_aks/spin_up_aks_cluster.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,20 @@ layout: learningpathall
88

99
## Project Overview
1010

11-
Arm CPUs are widely used in web server workloads on Kubernetes (k8s). In this Learning Path, you'll learn how to deploy [nginx](https://nginx.org/) on Arm-based CPUs within a hybrid architecture (x64 and arm64) K8s cluster on Azure's AKS.
11+
Arm CPUs are widely used in web server workloads on Kubernetes (k8s). In this Learning Path, you'll learn how to deploy [nginx](https://nginx.org/) on Arm-based CPUs within a heterogeneous (x64 and arm64) K8s cluster on Azure's AKS.
1212

13-
Many people begin their journey with Arm on K8s by adding Arm nodes to an existing x64-based cluster. This tutorial begins the same way.
13+
### Benefits of the multi-architecture approach
1414

15-
To begin, login to azure-cli, and bring up the initial AKS cluster:
15+
Many developers begin their journey with Arm on K8s by adding Arm nodes to an existing x64-based cluster. This has many advantages:
16+
17+
1. Since you are already familiar with K8s on x64, you can leverage that knowledge to quickly get the core components up and running.
18+
2. Leveraging the multi-architectural container image of your existing x64 workload expedites the migration to Arm with minimal deployment modifications.
19+
3. With both x64 and Arm workloads running in the same cluster, comparing performance across them is simplified.
20+
21+
Even if you don't already have an existing AKS cluster, you're covered, as this learning path will walk you through bringing up an initial AKS environment and nginx workload on x64. From there, you'll add Arm-based nodes running the same exact workload. You'll see how to smoke test it (simple tests to verify functionality), and then performance test it (slightly more involved) to better understand the performance characteristics of each architecture.
1622

1723
### Login to Azure via azure-cli
18-
If you haven't already, login to your Azure account using the Azure CLI:
24+
To begin, login to your Azure account using the Azure CLI:
1925

2026
```bash
2127
az login

0 commit comments

Comments
 (0)