Skip to content

Commit 9263eb2

Browse files
authored
editorial change
1 parent 16068b6 commit 9263eb2

1 file changed

Lines changed: 4 additions & 6 deletions

File tree

support/azure/azure-kubernetes/connectivity/cannot-access-cluster-api-server-using-authorized-ip-ranges.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Can't access the cluster API server using authorized IP ranges
33
description: Troubleshoot problems accessing the cluster API server when you use authorized IP address ranges in Azure Kubernetes Service (AKS).
44
ms.date: 03/20/2025
5-
ms.reviewer: chiragpa, nickoman, v-leedennis
5+
ms.reviewer: chiragpa, nickoman, wonkilee, v-leedennis
66
ms.service: azure-kubernetes-service
77
keywords:
88
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot access issues to the cluster API server when I use authorized IP address ranges so that I can work with my Azure Kubernetes Service (AKS) cluster successfully.
@@ -14,11 +14,9 @@ This article discusses how to resolve a scenario in which you can't use authoriz
1414

1515
## Symptoms
1616

17-
If you try to create or manage resources in an AKS cluster, you can't access the cluster API server.
18-
When you run `kubectl`, you receive the following error message:
19-
```
20-
Unable to connect to the server: dial tcp x.x.x.x:443: i/o timeout
21-
```
17+
If you try to create or manage resources in an AKS cluster, you can't access the cluster API server. When you run `kubectl`, you receive the following error message:
18+
19+
> Unable to connect to the server: dial tcp x.x.x.x:443: i/o timeout
2220
2321
## Cause
2422

0 commit comments

Comments
 (0)