Skip to content

Commit 57768b1

Browse files
authored
Merge pull request #291441 from paulth1/azure-operator-nexus-cluster-and-bmm
[AQ] edit pass: Azure operator nexus cluster and bmm
2 parents 5ca8858 + f4f3ae3 commit 57768b1

6 files changed

+775
-740
lines changed
Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: "Azure Operator Nexus: Accepted Cluster"
3-
description: Troubleshoot accepted Cluster resource.
2+
title: "Azure Operator Nexus: Accepted cluster"
3+
description: Learn how to troubleshoot accepted cluster resources.
44
author: matternst7258
55
ms.author: matthewernst
66
ms.service: azure-operator-nexus
@@ -10,45 +10,45 @@ ms.date: 10/30/2024
1010
# ms.custom: template-include
1111
---
1212

13-
# Troubleshoot accepted Cluster resources
13+
# Troubleshoot accepted cluster resources
1414

15-
Operator Nexus relies on mirroring, or hydrating, resources from the on-premises cluster to Azure. When this process is interrupted, the Cluster resource can move to `Accepted` state.
15+
Azure Operator Nexus relies on mirroring, or hydrating, resources from the on-premises cluster to Azure. When this process is interrupted, the cluster resource can move to the `Accepted` state.
1616

1717
## Diagnosis
1818

19-
The Cluster status is viewed via the Azure portal or via Azure CLI.
19+
The cluster status is viewed via the Azure portal or the Azure CLI.
2020

2121
```bash
2222
az networkcloud cluster show --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME>
2323
```
2424

2525
## Mitigation steps
2626

27-
### Triggering the resource sync
27+
Follow these steps for mitigation.
2828

29+
### Trigger the resource sync
2930

30-
1. From the Cluster resource page in the Azure portal, add a tag to the Cluster resource.
31-
2. The resource moves out of the `Accepted` state.
32-
33-
```bash
34-
az login
35-
az account set --subscription <SUBSCRIPTION>
36-
az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group <CLUSTER_RG> --resource-type "Microsoft.ContainerService/managedClusters"
37-
```
31+
1. From the cluster resource page in the Azure portal, add a tag to the cluster resource.
32+
1. The resource moves out of the `Accepted` state.
33+
34+
```bash
35+
az login
36+
az account set --subscription <SUBSCRIPTION>
37+
az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group <CLUSTER_RG> --resource-type "Microsoft.ContainerService/managedClusters"
38+
```
3839

3940
## Verification
4041

41-
After the tag is applied, the Cluster moves to `Running` state.
42+
After the tag is applied, the cluster moves to the `Running` state.
4243

4344
```bash
4445
az networkcloud cluster show --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME>
4546
```
4647

47-
If the Cluster resource maintains the state after a period of time, more than 5 minutes, contact Microsoft support.
48-
49-
## Further information
48+
If the cluster resource maintains the state for more than five minutes, contact Microsoft support.
5049

51-
Learn more about how resources are hydrated with [Azure Arc-enabled Kubernetes](/azure/azure-arc/kubernetes/overview).
50+
## Related content
5251

53-
If you still have questions, [contact support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
54-
For more information about Support plans, see [Azure Support plans](https://azure.microsoft.com/support/plans/response/).
52+
- For more information about how resources are hydrated, see [Azure Arc-enabled Kubernetes](/azure/azure-arc/kubernetes/overview).
53+
- If you still have questions, contact [Azure support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
54+
- For more information about support plans, see [Azure support plans](https://azure.microsoft.com/support/plans/response/).

0 commit comments

Comments
 (0)