ClusterIP, NodePort, LoadBalancer: Three Types, One Foundation
LoadBalancer and NodePort never replace ClusterIP: they add a layer on top of it. Understanding that stack avoids picking the wrong type by default.
LoadBalancer and NodePort never replace ClusterIP: they add a layer on top of it. Understanding that stack avoids picking the wrong type by default.
LoadBalancer et NodePort ne remplacent jamais ClusterIP : ils l'ajoutent en couche. Comprendre cet empilement évite de choisir le mauvais type de Service.
Un Service de type LoadBalancer reste en Pending indéfiniment sur un cluster on-premise, faute de cloud provider pour le satisfaire. Ce que MetalLB fait à la place.
A LoadBalancer Service stays Pending forever on an on-premise cluster, for lack of a cloud provider to satisfy it. What MetalLB does instead.