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: AKS-Hybrid/deploy-azure-container-registry.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy from a private container registry to on-premises Kubernetes using
3
3
description: Learn how to deploy from a private container registry to on-premises Kubernetes using Azure Container Registry and AKS enabled by Arc.
4
4
author: sethmanheim
5
5
ms.topic: how-to
6
-
ms.date: 11/02/2022
6
+
ms.date: 06/26/2024
7
7
ms.author: sethm
8
8
ms.lastreviewed: 03/16/2022
9
9
ms.reviewer: rbaziwane
@@ -20,7 +20,7 @@ This article describes how to deploy container images from a private container r
20
20
21
21
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.
22
22
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/).
24
24
25
25
## Prerequisites
26
26
@@ -39,7 +39,7 @@ In order to create a container registry, begin with a *resource group*. An Azure
39
39
az group create --name <RESOURCE_GROUP_NAME> --location eastus
40
40
```
41
41
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:
43
43
44
44
```azurecli
45
45
az acr create --resource-group <RESOURCE_GROUP_NAME> --name <REGISTRY_NAME> --sku Basic
Copy file name to clipboardExpand all lines: AKS-Hybrid/deploy-windows-application.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy Windows .NET applications
3
3
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.
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.
21
21
22
22
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).
23
23
@@ -31,7 +31,7 @@ Make sure you met the following requirements:
31
31
32
32
When you follow the procedures:
33
33
34
-
- Run the commands in a PowerShell administrative window.
34
+
- Run the commands in a PowerShell administrator window.
35
35
- 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).
36
36
37
37
## Deploy the application
@@ -92,7 +92,7 @@ spec:
92
92
93
93
Deploy the application using the `kubectl apply` command, and specify the name of your YAML manifest:
94
94
95
-
```console
95
+
```powershell
96
96
kubectl apply -f sample.yaml
97
97
```
98
98
@@ -109,11 +109,11 @@ When the application runs, a Kubernetes service exposes the application front en
109
109
110
110
To monitor progress, use the `kubectl get service` command with the `--watch` argument:
111
111
112
-
```PowerShell
112
+
```powershell
113
113
kubectl get service sample --watch
114
114
```
115
115
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**:
117
117
118
118
```output
119
119
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
137
137
138
138
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:
139
139
140
-
```console
140
+
```powershell
141
141
kubectl get pods -n default
142
142
```
143
143
144
144
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:
145
145
146
-
```console
146
+
```powershell
147
147
kubectl scale --replicas=3 deployment/sample
148
148
```
149
149
150
150
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:
0 commit comments