Skip to content

Commit 87f5dd6

Browse files
committed
More
1 parent 6488339 commit 87f5dd6

File tree

3 files changed

+13
-13
lines changed

3 files changed

+13
-13
lines changed

AKS-Hybrid/deploy-azure-container-registry.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy from a private container registry to on-premises Kubernetes using
33
description: Learn how to deploy from a private container registry to on-premises Kubernetes using Azure Container Registry and AKS enabled by Arc.
44
author: sethmanheim
55
ms.topic: how-to
6-
ms.date: 11/02/2022
6+
ms.date: 06/26/2024
77
ms.author: sethm
88
ms.lastreviewed: 03/16/2022
99
ms.reviewer: rbaziwane
@@ -20,7 +20,7 @@ This article describes how to deploy container images from a private container r
2020

2121
The article describes how to create a private container registry in Azure and push your container image to the private container registry. You can then deploy from the private registry to your on-premises Kubernetes cluster hosted in AKS enabled by Arc.
2222

23-
If you're interested in learning more about Container Registry in Azure, see the [Azure Container Registry documentation](/azure/container-registry/).
23+
For more information about Container Registry in Azure, see the [Azure Container Registry documentation](/azure/container-registry/).
2424

2525
## Prerequisites
2626

@@ -39,7 +39,7 @@ In order to create a container registry, begin with a *resource group*. An Azure
3939
az group create --name <RESOURCE_GROUP_NAME> --location eastus
4040
```
4141

42-
Create a Container Registry instance with the [az acr create](/cli/azure/acr) command, and provide your own registry name. The registry name must be unique within Azure and contain 5 to 50 alphanumeric characters. In the rest of this article, `<acrName>` is used as a placeholder for the container registry name, but you can provide your own unique registry name. The Basic SKU is a cost-optimized entry point for development purposes that provides a balance of storage and throughput.
42+
Create a Container Registry instance with the [az acr create](/cli/azure/acr) command, and provide your own registry name. The registry name must be unique within Azure and contain 5 to 50 alphanumeric characters. In the rest of this article, `<acrName>` is used as a placeholder for the container registry name, but you can provide your own unique registry name. The Basic SKU is a cost-optimized entry point for development purposes that provides a balance of storage and throughput:
4343

4444
```azurecli
4545
az acr create --resource-group <RESOURCE_GROUP_NAME> --name <REGISTRY_NAME> --sku Basic

AKS-Hybrid/deploy-windows-application.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy Windows .NET applications
33
description: Learn how to deploy a Windows.NET application to your Kubernetes cluster using a custom image stored in Azure Container Registry in AKS enabled by Azure Arc.
44
author: sethmanheim
55
ms.topic: tutorial
6-
ms.date: 11/01/2022
6+
ms.date: 06/26/2024
77
ms.author: sethm
88
ms.lastreviewed: 1/14/2022
99
ms.reviewer: abha
@@ -17,7 +17,7 @@ ms.reviewer: abha
1717

1818
[!INCLUDE [applies-to-azure stack-hci-and-windows-server-skus](includes/aks-hci-applies-to-skus/aks-hybrid-applies-to-azure-stack-hci-windows-server-sku.md)]
1919

20-
This tutorial describes how to deploy an ASP.NET sample application in a Windows Server container to the Azure Kubernetes Service (AKS) cluster in AKS enabled by Arc, and then test and scale your application. You also learn how to join a Windows node to an Active Directory domain.
20+
This tutorial describes how to deploy an ASP.NET sample application in a Windows Server container to the Azure Kubernetes Service (AKS) cluster in AKS enabled by Arc, then test and scale your application. You also learn how to join a Windows node to an Active Directory domain.
2121

2222
This tutorial assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for AKS enabled by Azure Arc](kubernetes-concepts.md).
2323

@@ -31,7 +31,7 @@ Make sure you met the following requirements:
3131

3232
When you follow the procedures:
3333

34-
- Run the commands in a PowerShell administrative window.
34+
- Run the commands in a PowerShell administrator window.
3535
- Ensure that OS-specific workloads land on the appropriate container host. If your Kubernetes cluster has a mixture of Linux and Windows worker nodes, you can use either node selectors or taints and tolerations. For more information, see [using node selectors and taints and tolerations](adapt-apps-mixed-os-clusters.md).
3636

3737
## Deploy the application
@@ -92,7 +92,7 @@ spec:
9292
9393
Deploy the application using the `kubectl apply` command, and specify the name of your YAML manifest:
9494

95-
```console
95+
```powershell
9696
kubectl apply -f sample.yaml
9797
```
9898

@@ -109,11 +109,11 @@ When the application runs, a Kubernetes service exposes the application front en
109109

110110
To monitor progress, use the `kubectl get service` command with the `--watch` argument:
111111

112-
```PowerShell
112+
```powershell
113113
kubectl get service sample --watch
114114
```
115115

116-
Initially, the **EXTERNAL-IP** for the **sample** service is shown as **pending**.
116+
Initially, the **EXTERNAL-IP** for the **sample** service is shown as **pending**:
117117

118118
```output
119119
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
@@ -137,19 +137,19 @@ If the connection times out when you try to load the page, verify whether the sa
137137

138138
We created a single replica of the application front end. To see the number and state of pods in your cluster, use the `kubectl get` command as follows:
139139

140-
```console
140+
```powershell
141141
kubectl get pods -n default
142142
```
143143

144144
To change the number of pods in the **sample** deployment, use the `kubectl scale` command. The following example increases the number of front-end pods to 3:
145145

146-
```console
146+
```powershell
147147
kubectl scale --replicas=3 deployment/sample
148148
```
149149

150150
Run `kubectl get pods` again to verify that the pods were created. After a minute or so, the additional pods are available in your cluster:
151151

152-
```console
152+
```powershell
153153
kubectl get pods -n default
154154
```
155155

AKS-Hybrid/monitor-logging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Monitoring and logging data
33
description: Learn how to create and access monitor and logging data for AKS enabled by Azure Arc.
44
author: sethmanheim
55
ms.topic: how-to
6-
ms.date: 10/24/2022
6+
ms.date: 06/26/2024
77
ms.author: sethm
88
ms.lastreviewed: 1/14/2022
99
ms.reviewer: abha

0 commit comments

Comments
 (0)