My setup is very similar and I ran into the same situation. This was a DNS issue for me.
If you have a private DNS zone with your private AKS cluster (should be in the resource group which was created for the AKS private cluster), go find the DNS record and IP address for the API server. Put that IP address into your hosts file (/etc/hosts if on linux or WSL) with the fully qualified domain name, then try your kubectl commands again.
发布评论
评论（1）
我的设置非常相似，我遇到了相同的情况。这对我来说是一个DNS问题。
如果您具有私有AKS群集的私有DNS区域（应该在为AKS私有群集创建的资源组中），请查找API服务器的DNS记录和IP地址。将该IP地址放入带有完全合格域名的Linux或WSL上的主机文件（/etc/hosts）中，然后再次尝试您的kubectl命令。
My setup is very similar and I ran into the same situation. This was a DNS issue for me.
If you have a private DNS zone with your private AKS cluster (should be in the resource group which was created for the AKS private cluster), go find the DNS record and IP address for the API server. Put that IP address into your hosts file (/etc/hosts if on linux or WSL) with the fully qualified domain name, then try your kubectl commands again.