Skip to content

Commit 7262e7f

Browse files
Fix build errors. Clean up deploy steps.
1 parent 1551aa8 commit 7262e7f

File tree

2 files changed

+34
-7
lines changed

2 files changed

+34
-7
lines changed

articles/aks/tutorial-kubernetes-deploy-application.md

Lines changed: 33 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,33 @@ AZD does not require a container registry step.
124124
125125
### [Azure CLI](#tab/azure-cli)
126126
127+
1. Deploy the application using the [`kubectl apply`][kubectl-apply] command, which parses the manifest file and creates the defined Kubernetes objects.
128+
129+
```console
130+
kubectl apply -f aks-store-quickstart.yaml
131+
```
132+
133+
The following example output shows the resources successfully created in the AKS cluster:
134+
135+
```output
136+
deployment.apps/rabbitmq created
137+
service/rabbitmq created
138+
deployment.apps/order-service created
139+
service/order-service created
140+
deployment.apps/product-service created
141+
service/product-service created
142+
deployment.apps/store-front created
143+
service/store-front created
144+
```
145+
146+
2. Check the deployment is successful by viewing the pods with `kubectl`
147+
148+
```console
149+
kubectl get pods
150+
```
151+
152+
### [Azure PowerShell](#tab/azure-powershell)
153+
127154
1. Deploy the application using the [`kubectl apply`][kubectl-apply] command, which parses the manifest file and creates the defined Kubernetes objects.
128155
129156
```console
@@ -163,7 +190,7 @@ You can change this later inside the `.azure/<your-env-name>/.env` file.
163190
164191
When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
165192
166-
### [Azure CLI](#tab/azure-cli)
193+
### Command Line
167194
168195
1. Monitor progress using the [`kubectl get service`][kubectl-get] command with the `--watch` argument.
169196
@@ -189,16 +216,15 @@ When the application runs, a Kubernetes service exposes the application front en
189216
190217
If the application doesn't load, it might be an authorization problem with your image registry. To view the status of your containers, use the `kubectl get pods` command. If you can't pull the container images, see [Authenticate with Azure Container Registry from Azure Kubernetes Service](cluster-container-registry-integration.md).
191218
192-
### [Azure Portal](#tab/azure-azd)
219+
### Azure Portal
193220
194-
You can navigate to your Azure Portal to find your deployment information.
221+
Navigate to your Azure Portal to find your deployment information.
195222
196-
1. Open your [Resource Group](azure-portal-rg)
223+
1. Open your [Resource Group][azure-rg] on the Azure Portal.
197224
2. Navigate to the Kubernetes service for your cluster
198225
3. Select `Services and Ingress` under `Kubernetes Resources`
199226
4. Copy the External IP shown in the column for store-front.
200-
201-
<!-- TODO: ADD IMAGE -->
227+
5. Paste the IP into your browser to visit your store page.
202228
203229
## Next steps
204230
@@ -216,6 +242,7 @@ In the next tutorial, you learn how to use PaaS services for stateful workloads
216242
> [Use PaaS services for stateful workloads in AKS][aks-tutorial-paas]
217243
218244
<!-- LINKS - external -->
245+
[azure-rg]:https://ms.portal.azure.com/#browse/resourcegroups
219246
[kubectl-apply]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply
220247
[kubectl-get]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#get
221248

articles/aks/tutorial-kubernetes-deploy-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -224,7 +224,7 @@ Sign in to your Azure Account through AZD configures your credentials.
224224
aks-nodepool1-19366578-vmss000003 Ready agent 47h v1.25.6
225225
```
226226
227-
[!INCLUDE [azd-login-ts](../includes/azd/azd-login-ts.md)]
227+
[!INCLUDE [azd-login-ts](./includes/azd/azd-login-ts.md)]
228228
229229
---
230230

0 commit comments

Comments
 (0)