Does Private Type AKS Cluster not support Automated Deployments?

Question

Does Private Type AKS Cluster not support Automated Deployments?

SUNGMIN JUNG 21

I'm trying to deploy applications using AKS automated deployments, but I think that Private Type AKS Clusters aren't supported.

There are several reasons for this.

First, automated deployments can't be performed via CLI or PowerShell. They can only be performed via Azure Portal, which requires specifying a namespace. Private AKS clusters can't be selected because their namespaces, deployments, and services aren't visible in the Azure console.

Furthermore, a self-hosted agent needs to be run when executing manifests, but this can't be specified when the DevOps Pipeline is automatically generated. Modifying this won't work either. Please confirm that Private Type AKS Clusters don't support automated deployments.

SUNGMIN JUNG 21 Reputation points

2025-08-14T00:46:40.0466667+00:00
Thanks for the follow-up. To be clear, I’m using the AKS Automated deployments wizard in the Azure Portal (not generic CI/CD).

On a Private AKS cluster the wizard fails at the very first step:

Namespace: “Failed to load all namespaces” → “Failed to create namespace 'namespace-workflow-…'”

PR/Apply: “Unable to reach the api server… Aks proxy api request took too long and was aborted.”

Because the wizard cannot even create the Pull Request, there’s no chance to switch the pipeline to a self-hosted agent afterward. Manually editing either YML or YAML to use a self-hosted agent does work, but that is outside the wizard.

Can you please confirm whether the Azure Portal Automated deployments wizard actually supports Private AKS today?
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-15T05:20:24.73+00:00

Hi SUNGMIN JUNG

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-18T16:21:52.2566667+00:00

Hi SUNGMIN JUNG

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
SUNGMIN JUNG 21 Reputation points

2025-08-19T02:56:27.8566667+00:00

Thanks for your answer, it solved what I was wondering about.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-19T15:57:52.0433333+00:00

Hi SUNGMIN JUNG

Thanks for your update.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.

Accepted answer

1 additional answer

Your answer

SUNGMIN JUNG 21 Reputation points

2025-08-14T00:46:40.0466667+00:00

Thanks for the follow-up. To be clear, I’m using the AKS Automated deployments wizard in the Azure Portal (not generic CI/CD).

On a Private AKS cluster the wizard fails at the very first step:

Namespace: “Failed to load all namespaces” → “Failed to create namespace 'namespace-workflow-…'”

PR/Apply: “Unable to reach the api server… Aks proxy api request took too long and was aborted.”

Because the wizard cannot even create the Pull Request, there’s no chance to switch the pipeline to a self-hosted agent afterward. Manually editing either YML or YAML to use a self-hosted agent does work, but that is outside the wizard.

Can you please confirm whether the Azure Portal Automated deployments wizard actually supports Private AKS today?
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-15T05:20:24.73+00:00

Hi SUNGMIN JUNG

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-18T16:21:52.2566667+00:00

Hi SUNGMIN JUNG

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
SUNGMIN JUNG 21 Reputation points

2025-08-19T02:56:27.8566667+00:00

Thanks for your answer, it solved what I was wondering about.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-19T15:57:52.0433333+00:00

Hi SUNGMIN JUNG

Thanks for your update.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.

Answer 1

Hi SUNGMIN JUNG

If it is not CI/CD, then the Azure Portal’s AKS Automated Deployments wizard does not support Private AKS clusters.

In a Private AKS cluster, the API server is not exposed publicly, so the wizard cannot load or create namespaces

The only supported way to deploy to private AKS today is outside the portal wizard:

Azure DevOps or GitHub Actions with a self-hosted agent in the same VNet as the AKS API server.
Direct kubectl from a VM or jumpbox in the VNet.

Hope this helps!

Please Let me know if you have any queries.

Answer 2

Hi SUNGMIN JUNG

As per the GitHub document - https://github.com/Azure/AKS/issues/4699Private AKS clusters do support automated deployments.

You can deploy to private clusters by setting up:

Set up a self-hosted agent in the same VNet as your Private AKS cluster to facilitate deployments.
A kubeconfig service connection that authenticates securely.
Consider manually configuring your Azure DevOps pipeline to ensure it uses the correct agent pool and can access the Private AKS cluster.

Additional References:

https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/windows-agent?view=azure-devops&tabs=IP-V4

Hope this helps!

Please Let me know if you have any queries.

Share via

Does Private Type AKS Cluster not support Automated Deployments?

1 additional answer

Your answer