Skip to content

Commit 5317f74

Browse files
authored
Merge pull request #227516 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 71b3970 + 53523be commit 5317f74

File tree

6 files changed

+8
-6
lines changed

6 files changed

+8
-6
lines changed

articles/aks/azure-cni-overlay.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address spa
4848
| Network configuration | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
4949
| Pod connectivity performance | Performance on par with VMs in a VNet | Additional hop adds minor latency |
5050
| Kubernetes Network Policies | Azure Network Policies, Calico, Cilium | Calico |
51-
| OS platforms supported | Linux and Windows | Linux only |
51+
| OS platforms supported | Linux and Windows Server 2022 | Linux only |
5252

5353
## IP address planning
5454

@@ -93,6 +93,7 @@ The overlay solution has the following limitations:
9393

9494
* Overlay can be enabled only for new clusters. Existing (already deployed) clusters can't be configured to use overlay.
9595
* You can't use Application Gateway as an Ingress Controller (AGIC) for an overlay cluster.
96+
* Windows Server 2019 node pools are not supported for overlay.
9697

9798
## Install the aks-preview Azure CLI extension
9899

articles/aks/csi-secrets-store-identity-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Azure AD workload identity (preview) is supported on both Windows and Linux clus
105105
usePodIdentity: "false"
106106
useVMManagedIdentity: "false"
107107
clientID: "${USER_ASSIGNED_CLIENT_ID}" # Setting this to use workload identity
108-
keyvaultName: ${$KEYVAULT_NAME} # Set to the name of your key vault
108+
keyvaultName: ${KEYVAULT_NAME} # Set to the name of your key vault
109109
cloudName: "" # [OPTIONAL for Azure] if not provided, the Azure environment defaults to AzurePublicCloud
110110
objects: |
111111
array:

articles/aks/private-clusters.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom: references_regions
1111

1212
In a private cluster, the control plane or API server has internal IP addresses that are defined in the [RFC1918 - Address Allocation for Private Internet][rfc1918-document] document. By using a private cluster, you can ensure network traffic between your API server and your node pools remains on the private network only.
1313

14-
The control plane or API server is in an Azure Kubernetes Service (AKS)-managed Azure subscription. Your cluster or node pool is in your subscription. The server and the cluster or node pool can communicate with each other through the [Azure Private Link service][private-link-service] in the API server virtual network and a private endpoint that's exposed on the subnet of your AKS cluster.
14+
The control plane or API server is in an Azure Kubernetes Service (AKS)-managed Azure resource group. Your cluster or node pool is in your resource group. The server and the cluster or node pool can communicate with each other through the [Azure Private Link service][private-link-service] in the API server virtual network and a private endpoint that's exposed on the subnet of your AKS cluster.
1515

1616
When you provision a private AKS cluster, AKS by default creates a private FQDN with a private DNS zone and an additional public FQDN with a corresponding A record in Azure public DNS. The agent nodes continue to use the A record in the private DNS zone to resolve the private IP address of the private endpoint for communication to the API server.
1717

articles/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,14 +63,15 @@ The following is the list of known limitations for Azure Synapse Link for SQL.
6363
* The security configuration from the source database will **NOT** be reflected in the target dedicated SQL pool.
6464
* Enabling Azure Synapse Link for SQL will create a new schema named `changefeed`. Don't use this schema, as it is reserved for system use.
6565
* Source tables with collations that are unsupported by dedicated SQL pools, such as UTF8 and certain Japanese collations, can't be replicated. Here's the [supported collations in Synapse SQL Pool](../sql/reference-collation-types.md).
66-
* Additionally, some Thai language collations are currently supported by Azure Synapse Link for SQL. These unsupported collations include:
66+
* Additionally, some Thai language collations are currently not supported by Azure Synapse Link for SQL. These unsupported collations include:
6767
* Thai100CaseInsensitiveAccentInsensitiveKanaSensitive
6868
* Thai100CaseInsensitiveAccentSensitiveSupplementaryCharacters
6969
* Thai100CaseSensitiveAccentInsensitiveKanaSensitive
7070
* Thai100CaseSensitiveAccentInsensitiveKanaSensitiveWidthSensitiveSupplementaryCharacters
7171
* Thai100CaseSensitiveAccentSensitiveKanaSensitive
7272
* Thai100CaseSensitiveAccentSensitiveSupplementaryCharacters
7373
* ThaiCaseSensitiveAccentInsensitiveWidthSensitive
74+
* Currently, the collation **Latin1_General_BIN2** is not supported as there is a known issue where the link cannot be stopped nor underlying tables could be removed from replication.
7475
* Single row updates (including off-page storage) of > 370 MB are not supported.
7576
* Currently, if the primary key column(s) of the table are not the first columns in the table, and columns to the left of primary key column(s) are deleted, replication may fail. To troubleshoot, see [Troubleshoot: Azure Synapse Link for SQL initial snapshot fails on source table with primary key not listed as the first column in sequence](troubleshoot/troubleshoot-sql-snapshot-primary-key-column-order.md).
7677

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -330,7 +330,7 @@ There is one type of modification to global scale set properties that does not f
330330
```
331331
332332
> [!NOTE]
333-
> The `az vmss reimage` command will reimage the selected instance, restoing him to the initial state. The instance may be restarted, and any local data will be lost.
333+
> The `az vmss reimage` command will reimage the selected instance, restoring it to the initial state. The instance may be restarted, and any local data will be lost.
334334
335335
- You can also use the language-specific [Azure SDKs](https://azure.microsoft.com/downloads/).
336336

articles/virtual-machines/linux/tutorial-custom-images.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ az sig image-version create \
133133
> [!NOTE]
134134
> You need to wait for the image version to completely finish being built and replicated before you can use the same managed image to create another image version.
135135
>
136-
> You can also store your image in Premiun storage by a adding `--storage-account-type premium_lrs`, or [Zone Redundant Storage](../../storage/common/storage-redundancy.md) by adding `--storage-account-type standard_zrs` when you create the image version.
136+
> You can also store your image in Premium storage by a adding `--storage-account-type premium_lrs`, or [Zone Redundant Storage](../../storage/common/storage-redundancy.md) by adding `--storage-account-type standard_zrs` when you create the image version.
137137
>
138138
139139

0 commit comments

Comments
 (0)