This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 57.99999999999999%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Get the following error when deploying a project from DevOps to AKS " Error: kuberntes cluster unreachable : get "https://##############-a0r7yt4o.0538e07b-5aa6-43e6-b5f2-c45781d9c9c0.privatelink.eastus.azmk8s.io:443/version":dial tcp 10.###.##.#:443: connect: connection refused
I guess your AKS cluster is a private one isn't it? Microsoft-hosted agents cannot access private AKS clusters unless connected via a private network. For private clusters, only clients in the same VNet (or peered VNet with proper NSG/routing) can access the cluster API. Do you have a private network for this?
If yes then deploy a self-hosted Azure DevOps agent inside the same VNet as the AKS cluster, or in a peered VNet with full access.
Hi @arko, yes, the setup is private, and we use a self-hosted agent that has been functioning well until now. However, it has suddenly stopped working. I suspect the problem lies within the cluster, as attempts to ping coredns directly from the pod are unsuccessful.
Okay. Let me check from backend. I have pinged you in private message. Please confirm on few things there. Thanks
Hello Mamdoh, any update on the requested details in the private message?
any update?