Skip to content

Commit 9d76056

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-stack-docs-pr into rb-shireen-2
2 parents ce61a2f + 9fc007a commit 9d76056

File tree

118 files changed

+1248
-7853
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

118 files changed

+1248
-7853
lines changed

.openpublishing.redirection.json

Lines changed: 186 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,190 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "azure-stack/mdc/azure-stack-capacity-planner.md",
5+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-capacity-planner",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "azure-stack/mdc/azure-stack-capacity-planning-overview.md",
10+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-capacity-planning-overview",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "azure-stack/mdc/azure-stack-gpu.md",
15+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-gpu",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "azure-stack/mdc/azure-stack-kubernetes-aks-engine-deploy-windows-tzl.md",
20+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-kubernetes-aks-engine-deploy-windows-tzl",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "azure-stack/mdc/azure-stack-manage-vm-protect-tzl.md",
25+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-manage-vm-protect-tzl",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "azure-stack/mdc/azure-stack-version-profiles-azurecli-2-tzl.md",
30+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-version-profiles-azurecli-2-tzl",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "azure-stack/mdc/azure-stack-vm-considerations.md",
35+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-vm-considerations",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "azure-stack/mdc/azure-stack-vm-sizes.md",
40+
"redirect_url": "/previous-versions/azure/mdc/azure-stack-vm-sizes",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "azure-stack/mdc/deployment-overview.md",
45+
"redirect_url": "/previous-versions/azure/mdc/deployment-overview",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "azure-stack/mdc/extended-storage-health-checks.md",
50+
"redirect_url": "/previous-versions/azure/mdc/extended-storage-health-checks",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "azure-stack/mdc/index.yml",
55+
"redirect_url": "/previous-versions/azure/mdc/index",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "azure-stack/mdc/integration-overview.md",
60+
"redirect_url": "/previous-versions/azure/mdc/integration-overview",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "azure-stack/mdc/mdc-overview.md",
65+
"redirect_url": "/previous-versions/azure/mdc/mdc-overview",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "azure-stack/mdc/network-appendix.md",
70+
"redirect_url": "/previous-versions/azure/mdc/network-appendix",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "azure-stack/mdc/network-configuration-lifecycle-management.md",
75+
"redirect_url": "/previous-versions/azure/mdc/network-configuration-lifecycle-management",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "azure-stack/mdc/network-deployment.md",
80+
"redirect_url": "/previous-versions/azure/mdc/network-deployment",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "azure-stack/mdc/network-integration.md",
85+
"redirect_url": "/previous-versions/azure/mdc/network-integration",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "azure-stack/mdc/network-introduction.md",
90+
"redirect_url": "/previous-versions/azure/mdc/network-introduction",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "azure-stack/mdc/oem-release-notes-mdc.md",
95+
"redirect_url": "/previous-versions/azure/mdc/oem-release-notes-mdc",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "azure-stack/mdc/operator/aks-refer-table-tzl.md",
100+
"redirect_url": "/previous-versions/azure/mdc/operator/aks-refer-table-tzl",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "azure-stack/mdc/operator/analyze-usage-tzl.md",
105+
"redirect_url": "/previous-versions/azure/mdc/operator/analyze-usage-tzl",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "azure-stack/mdc/operator/azure-stack-backup-back-up-azure-stack-tzl.md",
110+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-backup-back-up-azure-stack-tzl",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path": "azure-stack/mdc/operator/azure-stack-backup-best-practices-tzl.md",
115+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-backup-best-practices-tzl",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path": "azure-stack/mdc/operator/azure-stack-backup-enable-backup-console-tzl.md",
120+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-backup-enable-backup-console-tzl",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path": "azure-stack/mdc/operator/azure-stack-backup-enable-backup-powershell-tzl.md",
125+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-backup-enable-backup-powershell-tzl",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path": "azure-stack/mdc/operator/azure-stack-backup-infrastructure-backup-tzl.md",
130+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-backup-infrastructure-backup-tzl",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path": "azure-stack/mdc/operator/azure-stack-commvault-offer-tzl.md",
135+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-commvault-offer-tzl",
136+
"redirect_document_id": false
137+
},
138+
{
139+
"source_path": "azure-stack/mdc/operator/azure-stack-download-azure-marketplace-item-tca.md",
140+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-download-azure-marketplace-item-tca",
141+
"redirect_document_id": false
142+
},
143+
{
144+
"source_path": "azure-stack/mdc/operator/azure-stack-integrate-endpoints-tzl.md",
145+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-integrate-endpoints-tzl",
146+
"redirect_document_id": false
147+
},
148+
{
149+
"source_path": "azure-stack/mdc/operator/azure-stack-manage-basics-tzl.md",
150+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-manage-basics-tzl",
151+
"redirect_document_id": false
152+
},
153+
{
154+
"source_path": "azure-stack/mdc/operator/azure-stack-monitor-health-tzl.md",
155+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-monitor-health-tzl",
156+
"redirect_document_id": false
157+
},
158+
{
159+
"source_path": "azure-stack/mdc/operator/azure-stack-node-actions-tzl.md",
160+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-node-actions-tzl",
161+
"redirect_document_id": false
162+
},
163+
{
164+
"source_path": "azure-stack/mdc/operator/azure-stack-windows-server-faq-tzl.yml",
165+
"redirect_url": "/previous-versions/azure/mdc/operator/azure-stack-windows-server-faq-tzl",
166+
"redirect_document_id": false
167+
},
168+
{
169+
"source_path": "azure-stack/mdc/operator/billing-local-meters-tzl.md",
170+
"redirect_url": "/previous-versions/azure/mdc/operator/billing-local-meters-tzl",
171+
"redirect_document_id": false
172+
},
173+
{
174+
"source_path": "azure-stack/mdc/operator/billing-model-overview-tzl.md",
175+
"redirect_url": "/previous-versions/azure/mdc/operator/billing-model-overview-tzl",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path": "azure-stack/mdc/operator/integrated-dell-remote-access-controller-credentials.md",
180+
"redirect_url": "/previous-versions/azure/mdc/operator/integrated-dell-remote-access-controller-credentials",
181+
"redirect_document_id": false
182+
},
183+
{
184+
"source_path": "azure-stack/mdc/operator/registration-tzl.md",
185+
"redirect_url": "/previous-versions/azure/mdc/operator/registration-tzl",
186+
"redirect_document_id": false
187+
},
3188
{
4189
"source_path": "azure-local/release-information.md",
5190
"redirect_url": "/previous-versions/azure/azure-local/release-information",
@@ -2066,4 +2251,4 @@
20662251
"redirect_document_id": false
20672252
}
20682253
]
2069-
}
2254+
}

AKS-Arc/TOC.yml

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@
4747
- name: Quickstarts
4848
items:
4949
- name: Jumpstart HCIBox (external link)
50-
href: https://arcjumpstart.com/azure_jumpstart_hcibox/getting_started
50+
href: https://jumpstart.azure.com/azure_arc_jumpstart
5151
- name: How-to
5252
items:
5353
- name: Create Kubernetes clusters
@@ -159,12 +159,16 @@
159159
items:
160160
- name: Troubleshoot and known issues
161161
href: aks-troubleshoot.md
162+
- name: AKS on Azure Local support policy
163+
href: aks-on-azure-local-support-policy.md
164+
- name: Get support
165+
href: help-support.md
166+
- name: Use diagnostic checker
167+
href: aks-arc-diagnostic-checker.md
162168
- name: Control plane configuration validation errors
163169
href: control-plane-validation-errors.md
164170
- name: K8sVersionValidation error
165171
href: cluster-k8s-version.md
166-
- name: Use diagnostic checker
167-
href: aks-arc-diagnostic-checker.md
168172
- name: KubeAPIServer unreachable error
169173
href: kube-api-server-unreachable.md
170174
- name: Can't create/scale AKS cluster due to image issues
@@ -189,8 +193,12 @@
189193
href: network-validation-errors.md
190194
- name: Network validation error due to .local domain
191195
href: network-validation-error-local.md
196+
- name: Entra authentication prompts when running kubectl
197+
href: entra-prompts.md
192198
- name: BGP with FRR not working
193199
href: connectivity-troubleshoot.md
200+
- name: Cluster status stuck during upgrade
201+
href: cluster-upgrade-status.md
194202
- name: Reference
195203
items:
196204
- name: Azure CLI
@@ -603,8 +611,6 @@
603611
href: known-issues.yml
604612
- name: Support policies
605613
href: support-policies.md
606-
- name: Get support
607-
href: help-support.md
608614
- name: File bugs
609615
href: https://aka.ms/AKS-hybrid-issues
610616
- name: Release notes

AKS-Arc/aks-arc-diagnostic-checker.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to diagnose common causes for failures in AKS Arc.
44
ms.topic: troubleshooting
55
author: sethmanheim
66
ms.author: sethm
7-
ms.date: 01/30/2025
7+
ms.date: 06/27/2025
88
ms.reviewer: abha
99

1010
#Customer intent: As an AKS user, I want to use the diagnostic checker to run diagnostic checks on my AKS cluster to find out common causes for AKS cluster create failure.
@@ -13,14 +13,14 @@ ms.reviewer: abha
1313

1414
# Use the diagnostic checker to diagnose and fix environment issues for AKS cluster creation failure (preview)
1515

16-
It can be difficult to identify environment-related issues, such as networking configurations, that can result in an AKS cluster creation failure. The diagnostic checker is a PowerShell-based tool that can help you identify AKS cluster creation failures due to potential issues in the environment.
16+
It can be difficult to identify environment-related issues, such as networking configuration, that can result in an AKS cluster creation failure. The diagnostic checker is a PowerShell tool that can help you identify AKS cluster creation failures due to potential issues in the environment.
1717

1818
> [!NOTE]
19-
> You can only use the diagnostic checker tool if an AKS cluster was created, but is in a failed state. You can't use the tool if you don't see an AKS cluster on the Azure portal. If the AKS cluster creation fails before an Azure Resource Manager resource is created, [file a support request](aks-troubleshoot.md#open-a-support-request).
19+
> You can only use the diagnostic checker tool if an AKS cluster was created, but is in a failed state. You can't use the tool if you don't see an AKS cluster on the Azure portal. If the AKS cluster creation fails before an Azure Resource Manager resource is created, [file a support request](help-support.md).
2020
2121
## Before you begin
2222

23-
Before you begin, make sure you have the following prerequisites. If you don't meet the requirements for running the diagnostic checker tool, [file a support request](aks-troubleshoot.md#open-a-support-request):
23+
Before you begin, make sure you have the following prerequisites. If you don't meet the requirements for running the diagnostic checker tool, [file a support request](help-support.md):
2424

2525
- Direct access to the Azure Local cluster where you created the AKS cluster. This access can be through remote desktop (RDP), or you can also sign in to one of the Azure Local physical nodes.
2626
- Review the [networking concepts for creating an AKS cluster](aks-hci-network-system-requirements.md) and the [AKS cluster architecture](cluster-architecture.md).
@@ -43,17 +43,17 @@ VMName IPAddresses
4343
<cluster-name>-XXXXXX-control-plane-XXXXXX {172.16.0.10, 172.16.0.4, fe80::ec:d3ff:fea0:1}
4444
```
4545

46-
If you don't see a control plane VM as shown in the previous output, [file a support request](aks-troubleshoot.md#open-a-support-request).
46+
If you don't see a control plane VM as shown in the previous output, [file a support request](help-support.md).
4747

4848
If you see a control plane VM, and it has:
4949

50-
- 0 IPv4 addresses: file a [support request](aks-troubleshoot.md#open-a-support-request).
50+
- 0 IPv4 addresses: file a [support request](help-support.md).
5151
- 1 IP address: use the IPv4 address as the input for `vmIP` parameter.
5252
- 2 IP addresses: use any one of the IPv4 address as an input for `vmIP` parameter in the diagnostic checker.
5353

5454
## Run the diagnostic checker script
5555

56-
Copy the following PowerShell script `run_diagnostic.ps1` into any one node of your Azure Local cluster:
56+
Copy the following PowerShell script named `run_diagnostic.ps1` into any one node of your Azure Local cluster:
5757

5858
```powershell
5959
<#
@@ -288,4 +288,4 @@ The following table provides a summary of each test performed by the script, inc
288288

289289
## Next steps
290290

291-
If the problem persists, collect [AKS cluster logs](get-on-demand-logs.md) before you [create a support request](aks-troubleshoot.md#open-a-support-request).
291+
If the problem persists, collect [AKS cluster logs](get-on-demand-logs.md) before you [create a support request](help-support.md).

0 commit comments

Comments
 (0)