azure - AKS : How to get rid of load balancer?

Question

当你创建 Azure Kubernetes 服务 (AKS) 时，它会默认创建一个负载均衡器和一个用于访问它的网络集。它在单独的资源组中创建它。

但是，我们对此负载均衡器完全不感兴趣，因为我们将使用 Kubernetes 本身内配置的我们自己的负载均衡器/Ingress。

问题:如何避免在生成集群时一直生成 Azure 的负载均衡器？

Answer 1

在AKS Creation Without Public Load Balancer中进行了讨论github 问题及后续解释

It is possible the SLB IP is just for egress.

Let me try to clarify.

AKS with Basic Load Balancer

You can create it by passing the load balancer sku parameter Has implicit Egress (you won't see a public IP, although it is there on the Azure infrastructure) You can create private services accessible only through private IPs using the internal annotation. https://learn.microsoft.com/en-us/azure/aks/internal-lb AKS with Standard Load Balancer

Used by default on latest clientes, or explicitly by using the same parameter as above Has only explicit egress, which means if there isn't an egress IP the cluster won't have egress and will be broken. This is like the gateway to the internet IP. You can control, pre-create or change this IP (or have more than one) You can create private services accessible through private IPs using the internal annotation. https://learn.microsoft.com/en-us/azure/aks/internal-lb In some cases, enterprises might have egress defined via UDRs through a firewall etc. In which case that egress IP will not be used, and will be effectively not needed. But as of now it will be needed at create time as we don't know the egress path defined. We are no working on a UDR outbound type for SLB that will allow users to confirm they have egress through UDRs and in this case the SLB won't be created with a Public IP for egress

就像 @Sajeetharan 所问的那样 - 用例是什么？另外，如何强制要求您使用 AKS？也许同样的，您可以使用 kubeadm 集群更轻松地解决常规问题？

Deploying a Kubernetes cluster in Azure using kubeadm