Perfect timing as we are looking to shape our AKS service offering at work and looking into those considerations. Clear and concise as always. Thanks for your knowledge sharing.
Hi Geert, at minut 11:00 you describe that az cli assigned the Network Contributor role to the AKS subnet, but then again at 11:40 where the deployment failed as it was not able to link the VNet to the Private DNS Zone, you again mentioned that you just assigned the Network Contributor role to your user managed identity (I assume it’s again the subnet, as you call it out that you’re in the AKS subnet IAM blade). I’m confused here tbh. The Network Contributor role assignment originating from AZ CLI should be more than enough to link. Could you please explain ? PS. Great content, I really appreciate the effort and quality of your content!
Hi, When I am trying to create AKS private clusters am getting this error : - "Agents are unable to resolve Kubernetes API Server name. It's likely custom DNS is not configured correctly" and the creation is in failed state.. Could you provide any hint to resolve this?
Perfect timing as we are looking to shape our AKS service offering at work and looking into those considerations. Clear and concise as always. Thanks for your knowledge sharing.
Thank you! I am glad it is helpful.
Thank You, Sir! Your video was to the point. no unwanted contents for extending it. appreciate the effort
Hi Geert, at minut 11:00 you describe that az cli assigned the Network Contributor role to the AKS subnet, but then again at 11:40 where the deployment failed as it was not able to link the VNet to the Private DNS Zone, you again mentioned that you just assigned the Network Contributor role to your user managed identity (I assume it’s again the subnet, as you call it out that you’re in the AKS subnet IAM blade). I’m confused here tbh. The Network Contributor role assignment originating from AZ CLI should be more than enough to link. Could you please explain ? PS. Great content, I really appreciate the effort and quality of your content!
Hmm, I am not exactly sure what happened there. 😀 Indeed, granting access with the CLI once is enough.
Hi, When I am trying to create AKS private clusters am getting this error : - "Agents are unable to resolve Kubernetes API Server name. It's likely custom DNS is not configured correctly" and the creation is in failed state.. Could you provide any hint to resolve this?
Can we apply this in an existing private aks cluster? I.e. adding managed identity info
You mean adding managed identity to an existing private AKS cluster that uses SPs? Yes, az aks update would allow you to do that.
Hello, is there anyway to set this up on an already deployed cluster?
At this moment, you cannot convert existing AKS clusters into private clusters. New deployment I'm afraid...
is there a way to run kubectl cmds in cloudshell without using invoke command on private aks cluster?
There’s a way to configure cloud shell to use a virtual network. If it’s all wired up correctly, you should be able to use kubectl with private Aks.
Which tool you are using for diagrams?
I use Excalidraw mostly