Skip to content

Commit eaf1e9f

Browse files
authored
Update troubleshoot-dns-load-balancing.md
1 parent e5a6b66 commit eaf1e9f

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

support/azure/kubernetes-fleet/networking/troubleshoot-dns-load-balancing.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This article provides troubleshooting information for Azure Kubernetes Fleet Man
2626
2727
## Scenario 1: TrafficManagerProfile or Traffic Manager can't be created
2828
29-
This section provides common reasons and solutions for the `TrafficManagerProfile` Kubernetes object and its associated Azure Traffic Manager resource not being created screnarios.
29+
This section provides common reasons and solutions for the `TrafficManagerProfile` Kubernetes object and its associated Azure Traffic Manager resource not being created scenarios.
3030
3131
To determine the appropriate resolution, check the status of the `TrafficManagerProfile` object on the Fleet Manager hub cluster for the error message.
3232
@@ -36,11 +36,11 @@ kubectl get trafficmanagerprofile -n <namespace> <profile-name> -o yaml
3636

3737
### Error 1: The client does not have authorization to perform action
3838

39-
This issue may occur if one of the following conditions are met:
39+
This issue may occur if one of the following conditions is met:
4040

4141
* A nonexistent Azure resource group was specified in the `TrafficManagerProfile` manifest.
42-
* The resource group is not the same Azure Subscription as the Fleet Manager resource.
43-
* The Fleet Manager hub cluster identity does not have permission to create and manage Azure Traffic Manager profiles in the specified resource group.
42+
* The resource group isn't the same Azure Subscription as the Fleet Manager resource.
43+
* The Fleet Manager hub cluster identity doesn't have permission to create and manage Azure Traffic Manager profiles in the specified resource group.
4444

4545
You can check The `TrafficManagerProfile` status for details of the error. The following is the example of the TrafficManagerProfile status that shows the insufficient permissions issue.
4646

@@ -154,7 +154,7 @@ kubectl get trafficmanagerbackend -n <namespace> <backend-name> -o yaml
154154

155155
### Error 1: TrafficManagerProfile is not found or Invalid trafficManagerProfile
156156

157-
This issue may occur if one of the following conditions are met:
157+
This issue may occur if one of the following conditions is met:
158158

159159
- The `TrafficManagerBackend` was created in a different namespace than the `TrafficManagerProfile`.
160160
- The `TrafficManagerProfile` object exists, but the associated Azure Traffic Manager resource couldn't be found.
@@ -194,7 +194,7 @@ status:
194194

195195
### Error 2: Invalid Service or ServiceExport
196196

197-
This issue may occur if one of the following conditions are met:
197+
This issue may occur if one of the following conditions is met:
198198

199199
- The `Service` was created in a different namespace than the `TrafficManagerBackend`.
200200
- The `Service` exists, but the `ServiceExport` was not created in the same namespace as the `TrafficManagerBackend`.
@@ -236,7 +236,7 @@ conditions:
236236

237237
### Error 3: Azure Traffic Manager profile is not found
238238

239-
This issue may occur if one of the following conditions are met:
239+
This issue may occur if one of the following conditions is met:
240240

241241
- The `TrafficManagerProfile` was object exists, but the associated Azure Traffic Manager resource couldn't be found.
242242
- The Fleet Manager hub cluster identity doesn't have permission to create and manage Azure Traffic Manager profiles or endpoints in the specified resource group.

0 commit comments

Comments
 (0)