<p>I am currently using EKS private cluster with a public API server endpoint in order to use Azure DevOps environments(with Kubernetes service connection).</p>
<p>I have a requirement to make everything private in EKS.</p>
<p>Once EKS becomes private, it breaks everything in Azure DevOps as it is not able to reach the API server.</p>
<p>Any suggestion on how to communicate private kubernetes API server with azure devops would be appreciated.</p>

Jesus Vidal
<p>If you're trying to target the cluster for deployment, you need a self-hosted agent that has a network route to your cluster.</p>
<p>The other capabilities exposed by the environment feature of Azure DevOps (i.e. monitoring the state of the cluster via the environment view) will not work -- they require a public-facing Kubernetes API to work.</p>
