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/api-server-authorized-ip-ranges.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: API server authorized IP ranges in Azure Kubernetes Service (AKS)
3
3
description: Learn how to secure your cluster using an IP address range for access to the API server in Azure Kubernetes Service (AKS)
4
4
ms.topic: article
5
5
ms.custom: devx-track-azurecli
6
-
ms.date: 11/04/2022
6
+
ms.date: 12/26/2023
7
7
#Customer intent: As a cluster operator, I want to increase the security of my cluster by limiting access to the API server to only the IP addresses that I specify.
8
8
---
9
9
@@ -171,7 +171,7 @@ az aks update -g $RG -n $AKSNAME --api-server-authorized-ip-ranges $CURRENT_IP/2
171
171
> [!NOTE]
172
172
> The above example adds another IP address to the approved ranges. Note that it still includes the IP address from [Update a cluster's API server authorized IP ranges](#update-a-clusters-api-server-authorized-ip-ranges). If you don't include your existing IP address, this command will replace it with the new one instead of adding it to the authorized ranges. To disable authorized IP ranges, use `az aks update` and specify an empty range "".
173
173
174
-
Another option is to use the following command on Windows systems to get the public IPv4 address, or you can follow the steps in [Find your IP address](https://support.microsoft.com/en-gb/help/4026518/windows-10-find-your-ip-address).
174
+
Another option is to use the following command on Windows systems to get the public IPv4 address, or you can follow the steps in [Find your IP address](https://support.microsoft.com/help/4026518/windows-10-find-your-ip-address).
175
175
176
176
```azurepowershell-interactive
177
177
Invoke-RestMethod http://ipinfo.io/json | Select -exp ip
Copy file name to clipboardExpand all lines: articles/aks/concepts-network.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: Concepts - Networking in Azure Kubernetes Services (AKS)
3
3
description: Learn about networking in Azure Kubernetes Service (AKS), including kubenet and Azure CNI networking, ingress controllers, load balancers, and static IP addresses.
4
4
ms.topic: conceptual
5
-
ms.date: 12/01/2022
5
+
ms.date: 12/26/2023
6
6
ms.custom: fasttrack-edit
7
7
8
8
---
9
9
10
-
# Network concepts for applications in Azure Kubernetes Service (AKS)
10
+
# Networking concepts for applications in Azure Kubernetes Service (AKS)
11
11
12
12
In a container-based, microservices approach to application development, application components work together to process their tasks. Kubernetes provides various resources enabling this cooperation:
13
13
@@ -111,7 +111,6 @@ With Azure CNI, every pod gets an IP address from the subnet and can be accessed
111
111
> [!NOTE]
112
112
> Due to Kubernetes limitations, the Resource Group name, the Virtual Network name and the subnet name must be 63 characters or less.
113
113
114
-
115
114
Unlike kubenet, traffic to endpoints in the same virtual network isn't NAT'd to the node's primary IP. The source address for traffic inside the virtual network is the pod IP. Traffic that's external to the virtual network still NATs to the node's primary IP.
116
115
117
116
Nodes use the [Azure CNI][cni-networking] Kubernetes plugin.
Copy file name to clipboardExpand all lines: articles/aks/csi-secrets-store-identity-access.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,6 +67,9 @@ In this security model, the AKS cluster acts as token issuer. Microsoft Entra ID
67
67
68
68
4. Get the AKS cluster OIDC Issuer URL using the [`az aks show`][az-aks-show] command.
69
69
70
+
> [!NOTE]
71
+
> This step assumes you have an existing AKS cluster with the OIDC Issuer URL enabled. If you don't have it enabled, see [Update an AKS cluster with OIDC Issuer](./use-oidc-issuer.md#update-an-aks-cluster-with-oidc-issuer) to enable it.
72
+
70
73
```bash
71
74
export AKS_OIDC_ISSUER="$(az aks show --resource-group $RESOURCE_GROUP --name $CLUSTER_NAME --query "oidcIssuerProfile.issuerUrl" -o tsv)"
72
75
echo $AKS_OIDC_ISSUER
@@ -116,11 +119,11 @@ In this security model, the AKS cluster acts as token issuer. Microsoft Entra ID
116
119
objects: |
117
120
array:
118
121
- |
119
-
objectName: secret1
122
+
objectName: secret1 # Set to the name of your secret
120
123
objectType: secret # object types: secret, key, or cert
121
124
objectVersion: "" # [OPTIONAL] object versions, default to latest if empty
122
125
- |
123
-
objectName: key1
126
+
objectName: key1 # Set to the name of your key
124
127
objectType: key
125
128
objectVersion: ""
126
129
tenantId: "${IDENTITY_TENANT}" # The tenant ID of the key vault
Copy file name to clipboardExpand all lines: articles/aks/integrations.md
+25-17Lines changed: 25 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Azure Kubernetes Service (AKS) provides extra functionality for your clusters us
12
12
13
13
## Add-ons
14
14
15
-
Add-ons are a fully supported way to provide extra capabilities for your AKS cluster. The installation, configuration, and lifecycle of add-ons is managed by AKS. You can use the [`az aks enable-addons`][az-aks-enable-addons] command to install an add-on or manage the add-ons for your cluster.
15
+
Add-ons are a fully supported way to provide extra capabilities for your AKS cluster. The installation, configuration, and lifecycle of add-ons are managed on AKS. You can use the [`az aks enable-addons`][az-aks-enable-addons] command to install an add-on or manage the add-ons for your cluster.
16
16
17
17
AKS uses the following rules for applying updates to installed add-ons:
18
18
@@ -24,21 +24,21 @@ AKS uses the following rules for applying updates to installed add-ons:
24
24
### Exceptions
25
25
26
26
- Add-ons are upgraded to a new major/minor version (or breaking change) within a Kubernetes minor version if either the cluster's Kubernetes version or the add-on version are in preview.
27
-
- There may be unavoidable circumstances, such as CVE security patches or critical bug fixes, when you need to update an add-on within a GA minor version.
27
+
- There can be unavoidable circumstances, such as CVE security patches or critical bug fixes, when you need to update an add-on within a GA minor version.
28
28
29
29
### Available add-ons
30
30
31
-
| Name | Description |More details|
32
-
|---|---|---|
33
-
| web_application_routing | Use a managed NGINX ingress controller with your AKS cluster.|[Application Routing Overview][app-routing]|
34
-
| ingress-appgw | Use Application Gateway Ingress Controller with your AKS cluster. |[What is Application Gateway Ingress Controller?][agic]|
35
-
| keda | Use event-driven autoscaling for the applications on your AKS cluster. |[Simplified application autoscaling with Kubernetes Event-driven Autoscaling (KEDA) add-on][keda]|
36
-
| monitoring | Use Container Insights monitoring with your AKS cluster. |[Container insights overview][container-insights]|
37
-
| azure-policy | Use Azure Policy for AKS, which enables at-scale enforcements and safeguards on your clusters in a centralized, consistent manner. |[Understand Azure Policy for Kubernetes clusters][azure-policy-aks]|
38
-
| azure-keyvault-secrets-provider | Use Azure Keyvault Secrets Provider addon.|[Use the Azure Key Vault Provider for Secrets Store CSI Driver in an AKS cluster][keyvault-secret-provider]|
39
-
| virtual-node | Use virtual nodes with your AKS cluster. |[Use virtual nodes][virtual-nodes]|
40
-
| http_application_routing | Configure ingress with automatic public DNS name creation for your AKS cluster (retired). |[HTTP application routing add-on on Azure Kubernetes Service (AKS) (retired)][http-app-routing]|
41
-
| open-service-mesh | Use Open Service Mesh with your AKS cluster (retired). |[Open Service Mesh AKS add-on (retired)][osm]|
31
+
| Name | Description |Articles | GitHub|
32
+
|---|---|---| --- |
33
+
| web_application_routing | Use a managed NGINX ingress controller with your AKS cluster.|[Application Routing Overview][app-routing]|[GitHub][app-routing-repo]|
34
+
| ingress-appgw | Use Application Gateway Ingress Controller with your AKS cluster. |[What is Application Gateway Ingress Controller?][agic]|[GitHub][agic-repo]|
35
+
| keda | Use event-driven autoscaling for the applications on your AKS cluster. |[Simplified application autoscaling with Kubernetes Event-driven Autoscaling (KEDA) add-on][keda]|[GitHub][keda-repo]|
36
+
| monitoring | Use Container Insights monitoring with your AKS cluster. |[Container insights overview][container-insights]|[GitHub][aks-repo]|
37
+
| azure-policy | Use Azure Policy for AKS, which enables at-scale enforcements and safeguards on your clusters in a centralized, consistent manner. |[Understand Azure Policy for Kubernetes clusters][azure-policy-aks]|[GitHub][azure-policy-repo]|
38
+
| azure-keyvault-secrets-provider | Use Azure Keyvault Secrets Provider addon.|[Use the Azure Key Vault Provider for Secrets Store CSI Driver in an AKS cluster][keyvault-secret-provider]|[GitHub][keyvault-secret-provider-repo]|
39
+
| virtual-node | Use virtual nodes with your AKS cluster. |[Use virtual nodes][virtual-nodes]|[GitHub][virtual-nodes-oss-repo]|
40
+
| http_application_routing | Configure ingress with automatic public DNS name creation for your AKS cluster (retired). |[HTTP application routing add-on on Azure Kubernetes Service (AKS) (retired)][http-app-routing]|[GitHub][app-routing-repo]|
41
+
| open-service-mesh | Use Open Service Mesh with your AKS cluster (retired). |[Open Service Mesh AKS add-on (retired)][osm]|[GitHub][osm-repo]|
42
42
43
43
## Extensions
44
44
@@ -53,7 +53,7 @@ Extensions and add-ons are both supported ways to add functionality to your AKS
53
53
54
54
## GitHub Actions
55
55
56
-
GitHub Actions helps you automate your software development workflows from within GitHub.
56
+
GitHub Actions help you automate your software development workflows from within GitHub.
57
57
58
58
- For more information on using GitHub Actions with Azure, see [GitHub Actions for Azure][github-actions].
59
59
- For an example of using GitHub Actions with an AKS cluster, see [Build, test, and deploy containers to Azure Kubernetes Service using GitHub Actions][github-actions-aks].
@@ -69,25 +69,32 @@ There are many open-source and third-party integrations you can install on your
69
69
|[Grafana][grafana]| An open-source dashboard for observability. |[Deploy Grafana on Kubernetes][grafana-install] or use [Managed Grafana][managed-grafana]|
70
70
|[Couchbase][couchdb]| A distributed NoSQL cloud database. |[Install Couchbase and the Operator on AKS][couchdb-install]|
71
71
|[OpenFaaS][open-faas]| An open-source framework for building serverless functions by using containers. |[Use OpenFaaS with AKS][open-faas-aks]|
72
-
|[Apache Spark][apache-spark]| An open-source, fast engine for large-scale data processing. | Running Apache Spark jobs requires a minimum node size of *Standard_D3_v2*. See [running Spark on Kubernetes][spark-kubernetes] for more details on running Spark jobs on Kubernetes. |
72
+
|[Apache Spark][apache-spark]| An open-source, fast engine for large-scale data processing. | Running Apache Spark jobs requires a minimum node size of *Standard_D3_v2*. For more information on running Spark jobs on Kubernetes, see the [running Spark on Kubernetes][spark-kubernetes] guide. |
73
73
|[Istio][istio]| An open-source service mesh. |[Istio Installation Guides][istio-install]|
74
74
|[Linkerd][linkerd]| An open-source service mesh. |[Linkerd Getting Started][linkerd-install]|
75
75
|[Consul][consul]| An open-source, identity-based networking solution. |[Getting Started with Consul Service Mesh for Kubernetes][consul-install]|
76
76
77
77
### Third-party integrations for Windows containers
78
78
79
-
Microsoft has collaborated with partners to ensure your build, test, deployment, configuration, and monitoring of your applications perform optimally with Windows containers on AKS.
79
+
Microsoft collaborates with partners to ensure the build, test, deployment, configuration, and monitoring of your applications perform optimally with Windows containers on AKS.
80
80
81
-
For more details, see [Windows AKS partner solutions][windows-aks-partner-solutions].
81
+
For more information, see [Windows AKS partner solutions][windows-aks-partner-solutions].
@@ -38,7 +38,7 @@ The following limitations apply when you create and manage AKS clusters that sup
38
38
39
39
## System and user node pools
40
40
41
-
For a system node pool, AKS automatically assigns the label **kubernetes.azure.com/mode: system** to its nodes. This causes AKS to prefer scheduling system pods on node pools that contain this label. This label doesn't prevent you from scheduling application pods on system node pools. However, we recommend you isolate critical system pods from your application pods to prevent misconfigured or rogue application pods from accidentally killing system pods.
41
+
For a system node pool, AKS automatically assigns the label **kubernetes.azure.com/mode: system** to its nodes. This causes AKS to prefer scheduling system pods on node pools that contain this label. This label doesn't prevent you from scheduling application pods on system node pools. However, we recommend you isolate critical system pods from your application pods to prevent misconfigured or rogue application pods from accidentally deleting system pods.
42
42
43
43
You can enforce this behavior by creating a dedicated system node pool. Use the `CriticalAddonsOnly=true:NoSchedule` taint to prevent application pods from being scheduled on system node pools.
You can add one or more system node pools to existing AKS clusters. It's recommended to schedule your application pods on user node pools, and dedicate system node pools to only critical system pods. This prevents rogue application pods from accidentally killing system pods. Enforce this behavior with the `CriticalAddonsOnly=true:NoSchedule`[taint][aks-taints] for your system node pools.
109
+
You can add one or more system node pools to existing AKS clusters. It's recommended to schedule your application pods on user node pools, and dedicate system node pools to only critical system pods. This prevents rogue application pods from accidentally deleting system pods. Enforce this behavior with the `CriticalAddonsOnly=true:NoSchedule`[taint][aks-taints] for your system node pools.
110
110
111
111
The following command adds a dedicated node pool of mode type system with a default count of three nodes.
112
112
@@ -122,7 +122,7 @@ az aks nodepool add \
122
122
123
123
### [Azure PowerShell](#tab/azure-powershell)
124
124
125
-
You can add one or more system node pools to existing AKS clusters. It's recommended to schedule your application pods on user node pools, and dedicate system node pools to only critical system pods. Adding more system node pools prevents rogue application pods from accidentally killing system pods. Enforce the behavior with the `CriticalAddonsOnly=true:NoSchedule`[taint][aks-taints] for your system node pools.
125
+
You can add one or more system node pools to existing AKS clusters. It's recommended to schedule your application pods on user node pools, and dedicate system node pools to only critical system pods. Adding more system node pools prevents rogue application pods from accidentally deleting system pods. Enforce the behavior with the `CriticalAddonsOnly=true:NoSchedule`[taint][aks-taints] for your system node pools.
126
126
127
127
The following command adds a dedicated node pool of mode type system with a default count of three nodes.
0 commit comments