You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/learn/quick-kubernetes-deploy-azd.md
+10-14Lines changed: 10 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ The `azd` template contains all the code needed to create the services, but you
97
97
98
98
## Create and deploy resources for your cluster
99
99
100
-
`azd` runs all the hooks inside of the [`azd-hooks` folder](https://github.com/Azure-Samples/aks-store-demo/tree/main/azd-hooks) to preregister, provision, and deploy the application services.
100
+
`azd` runs all the hooks inside of the [`azd-hooks` folder][azd-hooks-folder] to preregister, provision, and deploy the application services.
101
101
102
102
The `azd` template for this quickstart creates a new resource group with an AKS cluster and an Azure key vault. The key vault stores client secrets and runs the services in the `pets` namespace
103
103
@@ -135,15 +135,19 @@ The `azd` template for this quickstart creates a new resource group with an AKS
135
135
136
136
## Test the application
137
137
138
-
When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
138
+
When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete. To manage a Kubernetes cluster, use the Kubernetes command-line client, [kubectl][kubectl]. `kubectl` is already installed during `azd up`.
139
139
140
140
1. Set your namespace as the demo namespace `pets` using the [`kubectl set-context`][kubectl-set-context] command.
2. Check the status of the deployed pods using the [`kubectl get pods`][kubectl-get-pods] command. Make sure all pods are `Running` before proceeding.
146
+
2. Check the status of the deployed pods using the [`kubectl get pods`][kubectl-get] command. Make sure all pods are `Running` before proceeding.
147
+
148
+
```console
149
+
kubectl get pods
150
+
```
147
151
148
152
3. Check for a public IP address for the store-front application and monitor progress using the [`kubectl get service`][kubectl-get] command with the `--watch` argument.
149
153
@@ -175,7 +179,7 @@ When the application runs, a Kubernetes service exposes the application front en
175
179
176
180
Once you're finished with the quickstart, clean up unnecessary resources to avoid Azure charges.
177
181
178
-
1. Delete all the resources created in the quickstart using the [`azd down`][az-down] command.
182
+
1. Delete all the resources created in the quickstart using the [`azd down`][azd-down] command.
179
183
180
184
```azdeveloper
181
185
azd down
@@ -215,26 +219,18 @@ To learn more about AKS and walk through a complete code-to-deployment example,
0 commit comments