Skip to content

Commit 75e55de

Browse files
author
naman-msft
committed
updated docs;
1 parent 2d85d21 commit 75e55de

File tree

4 files changed

+0
-72
lines changed

4 files changed

+0
-72
lines changed

scenarios/DeployCassandraOnAKS/deploy-cassandra-on-aks.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ In this tutorial, you'll deploy an open-source Apache Cassandra cluster on Azure
1717
1. Install Azure CLI. You can follow [Install the Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli) for instructions.
1818
2. Install `kubectl`. You can use the `az aks install-cli` command to install it if you are using Azure Cloud Shell.
1919

20-
---
2120

2221
## Step 1: Create an AKS Cluster
2322

@@ -64,8 +63,6 @@ az aks create \
6463
--generate-ssh-keys
6564
```
6665

67-
---
68-
6966
## Step 2: Connect to the AKS Cluster
7067

7168
Retrieve the AKS cluster credentials and configure `kubectl`.
@@ -93,8 +90,6 @@ aks-nodepool1-xxxxx-vmss000001 Ready agent 3m52s v1.26.0
9390
aks-nodepool1-xxxxx-vmss000002 Ready agent 3m48s v1.26.0
9491
```
9592

96-
---
97-
9893
## Step 3: Deploy the Cassandra Cluster
9994

10095
Create a Kubernetes manifest file in Cloud Shell to define the Cassandra deployment. Use a name like `cassandra-deployment.yaml`.
@@ -141,8 +136,6 @@ Results:
141136
statefulset.apps/cassandra created
142137
```
143138

144-
---
145-
146139
## Step 4: Create a Headless Service for Cassandra
147140

148141
Create a Kubernetes manifest file in Cloud Shell to define the Cassandra headless service. Use a name like `cassandra-service.yaml`.
@@ -168,7 +161,6 @@ EOF
168161
kubectl apply -f cassandra-service.yaml
169162
```
170163

171-
172164
## Step 4: Verify Cassandra Deployment
173165

174166
Check the status of the Cassandra pods to ensure deployment is successful.
@@ -219,8 +211,6 @@ NAME READY AGE
219211
cassandra 3/3 3m
220212
```
221213

222-
---
223-
224214
## Step 5: Access Cassandra Cluster
225215

226216
Create a temporary Pod to access the Cassandra cluster using `cqlsh`, the Cassandra query tool.
@@ -250,8 +240,6 @@ Connected to Test Cluster at cassandra-0.cassandra:9042.
250240
Use HELP for help.
251241
```
252242

253-
---
254-
255243
This tutorial deployed an Apache Cassandra cluster on AKS. You managed the cluster using Kubernetes manifests and verified its deployment.
256244

257245
> **IMPORTANT:** Do not forget to clean up unnecessary resources like the AKS cluster if you no longer need them.

scenarios/DeployClickhouseOnAKS/deploy-clickhouse-on-aks.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,6 @@ Ensure that you have the following:
2121
3. Access to `kubectl` CLI to manage your Kubernetes cluster.
2222
4. Azure CLI extensions enabled for AKS (`az extension add --name aks`).
2323

24-
---
25-
2624
## Step 1: Create a Resource Group
2725

2826
Create a new Azure resource group to contain all resources related to the deployment.
@@ -52,8 +50,6 @@ Results:
5250
}
5351
```
5452

55-
---
56-
5753
## Step 2: Create an AKS Cluster
5854

5955
Create an Azure Kubernetes Service (AKS) cluster in the resource group.
@@ -63,8 +59,6 @@ export MY_AKS_CLUSTER="MyAKSCluster$RANDOM_SUFFIX"
6359
az aks create --resource-group $MY_RESOURCE_GROUP --name $MY_AKS_CLUSTER --node-count 3 --generate-ssh-keys
6460
```
6561

66-
---
67-
6862
## Step 3: Connect to the AKS Cluster
6963

7064
Obtain the Kubernetes credentials to connect to your AKS cluster.
@@ -81,8 +75,6 @@ Results:
8175
Merged "MyAKSClusterxxx" as current context in /home/user/.kube/config
8276
```
8377

84-
---
85-
8678
## Step 4: Create a Namespace for ClickHouse
8779

8880
Create a Kubernetes namespace to host the ClickHouse deployment.
@@ -99,8 +91,6 @@ Results:
9991
namespace/clickhouse created
10092
```
10193

102-
---
103-
10494
## Step 5: Deploy ClickHouse on AKS
10595

10696
Use the following Kubernetes manifest to deploy ClickHouse. Save this manifest into a file named **clickhouse-deployment.yaml**.
@@ -167,8 +157,6 @@ statefulset.apps/clickhouse created
167157
persistentvolumeclaim/clickhouse-pvc created
168158
```
169159

170-
---
171-
172160
## Step 6: Verify the Deployment
173161

174162
Check if the ClickHouse pods are running correctly:
@@ -204,8 +192,6 @@ clickhouse-1 1/1 Running 0 2m
204192
clickhouse-2 1/1 Running 0 2m
205193
```
206194

207-
---
208-
209195
## Summary
210196

211197
You have successfully deployed a ClickHouse cluster on AKS. You can now connect to the ClickHouse service using the appropriate service endpoint or Kubernetes port forwarding.

scenarios/DeployTensorflowOnAKS/deploy-tensorflow-on-aks.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ ms.custom: devx-track-azurecli, mode-api, innovation-engine, machine-learning, k
1212

1313
This guide demonstrates how to deploy a Tensorflow cluster on AKS using the Azure CLI. The setup includes provisioning an AKS cluster, configuring a Kubernetes namespace, and deploying a TensorFlow cluster.
1414

15-
---
1615

1716
## Prerequisites
1817

@@ -22,7 +21,6 @@ This guide demonstrates how to deploy a Tensorflow cluster on AKS using the Azur
2221

2322
> **Note:** Please make sure you are logged into Azure and have set your subscription in advance.
2423
25-
---
2624

2725
## Step 1: Create a Resource Group
2826

@@ -53,8 +51,6 @@ Results:
5351
}
5452
```
5553

56-
---
57-
5854
## Step 2: Create an AKS Cluster
5955

6056
Provision an AKS cluster in the resource group.
@@ -64,7 +60,6 @@ export AKS_CLUSTER_NAME="AKS-TF-Cluster-$RANDOM_SUFFIX"
6460
az aks create --name $AKS_CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --node-count 3 --enable-addons monitoring --generate-ssh-keys
6561
```
6662

67-
---
6863

6964
## Step 3: Connect to the AKS Cluster
7065

@@ -74,16 +69,6 @@ Obtain the cluster credentials and configure `kubectl` to use the newly created
7469
az aks get-credentials --name $AKS_CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME
7570
```
7671

77-
Results:
78-
79-
<!-- expected_similarity=0.3 -->
80-
81-
```text
82-
Merged "AKS-TF-Cluster-xxx" as current context in /home/username/.kube/config
83-
```
84-
85-
---
86-
8772
## Step 4: Create a Kubernetes Namespace for TensorFlow
8873

8974
Create a namespace to organize resources related to TensorFlow.
@@ -101,8 +86,6 @@ Results:
10186
namespace/tensorflow-cluster created
10287
```
10388

104-
---
105-
10689
## Step 5: Prepare TensorFlow Deployment Configuration
10790

10891
Create the TensorFlow deployment configuration file.
@@ -132,8 +115,6 @@ spec:
132115
EOF
133116
```
134117

135-
---
136-
137118
## Step 6: Deploy the TensorFlow Cluster
138119

139120
Deploy the TensorFlow cluster by applying the configuration file.
@@ -150,8 +131,6 @@ Results:
150131
deployment.apps/tensorflow-deployment created
151132
```
152133

153-
---
154-
155134
## Step 7: Create a LoadBalancer Service for TensorFlow
156135

157136
Expose the TensorFlow deployment using a LoadBalancer service to make it accessible externally.
@@ -184,8 +163,6 @@ Results:
184163
service/tensorflow-service created
185164
```
186165

187-
---
188-
189166
## Step 8: Check Service External IP
190167

191168
Retrieve the external IP address of the TensorFlow service.

scenarios/DeployTrinoOnAKS/deploy-trino-on-aks.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ In this Exec Doc, you will learn how to deploy a Trino (formerly PrestoSQL) clus
1717
1. Ensure you have Azure CLI installed in your environment or use [Azure Cloud Shell](https://shell.azure.com/).
1818
2. Ensure a Kubernetes cluster is already deployed on AKS. You can create one using [this guide](https://learn.microsoft.com/azure/aks/).
1919

20-
---
2120

2221
## Step 2: Create Azure Resource Group
2322

@@ -49,8 +48,6 @@ Results:
4948
}
5049
```
5150

52-
---
53-
5451
## Step 3: Create AKS Cluster
5552

5653
We will deploy an AKS cluster to host the Trino cluster.
@@ -66,8 +63,6 @@ az aks create \
6663
--generate-ssh-keys
6764
```
6865

69-
---
70-
7166
## Step 4: Configure `kubectl` Access
7267

7368
We will configure `kubectl` to connect to the newly created AKS cluster.
@@ -76,16 +71,6 @@ We will configure `kubectl` to connect to the newly created AKS cluster.
7671
az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $AKS_CLUSTER_NAME
7772
```
7873

79-
Results:
80-
81-
<!-- expected_similarity=0.3 -->
82-
83-
```text
84-
Merged "TrinoAKSClusterxxx" as the current context in /home/.kube/config
85-
```
86-
87-
---
88-
8974
## Step 5: Create Namespace for Trino
9075

9176
Namespaces help organize your Kubernetes resources.
@@ -112,8 +97,6 @@ Results:
11297
}
11398
```
11499

115-
---
116-
117100
## Step 6: Deploy Trino on AKS
118101

119102
We will use a Kubernetes manifest to deploy the Trino cluster.
@@ -159,8 +142,6 @@ Results:
159142
deployment.apps/trino created
160143
```
161144

162-
---
163-
164145
## Step 7: Expose Trino Service
165146

166147
Expose the Trino deployment via a Kubernetes service for external access.
@@ -182,7 +163,6 @@ Results:
182163
service/trino-service exposed
183164
```
184165

185-
---
186166

187167
## Step 8: Verify Deployment
188168

@@ -218,8 +198,6 @@ trino-xxxxx-xxxxx 1/1 Running 0 5m
218198
trino-xxxxx-xxxxx 1/1 Running 0 5m
219199
```
220200

221-
---
222-
223201
## Step 9: Fetch Service Public IP
224202

225203
Retrieve the external IP address of the Trino service.
@@ -239,6 +217,5 @@ External IP: xx.xx.xx.xx
239217

240218
The `EXTERNAL-IP` field contains the Trino service's public IP. Visit `http://<EXTERNAL-IP>:8080` to access the Trino cluster.
241219

242-
---
243220

244221
You have successfully deployed a Trino cluster on Azure Kubernetes Service! 🎉

0 commit comments

Comments
 (0)