container-native load balancing

Related topics

• container-native load balancing depends on network endpoint groups From the official documentation: “Container-native load balancing is the practice of evenly distributing traffic directly to the IP addresses of individual Pods (rather than nodes) using the `GCE_VM_IP_PORT` NEGs.”
• container-native load balancing is part of GKE From the official documentation: “Verifies if container-native load balancing is enabled on a GKE cluster.”
• Cloud Load Balancing works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh works with Cloud Load Balancing to provide a managed ingress experience.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Service Mesh works with network endpoint groups From the official documentation: “Later, this deployment guide discusses how you can configure these NEGs as backends for Cloud Service Mesh services.”
• Cloud Load Balancing is an alternative to Cloud Service Mesh From the official documentation: “If you want to use [Cloud Load Balancing, Ingress, or Cloud Service Mesh to handle the SSL configuration](/migrate/containers/docs/windows/prepare-windows-cluster#secure-access), then you need to set `protocol` to `http`:”
• Cloud Load Balancing works with GKE From the official documentation: “GKE and GKE Enterprise network controllers also support the deployment of Cloud Load Balancing for built-in integration with container networking.”
• Cloud Load Balancing works with network endpoint groups From the official documentation: “- **[Network endpoint groups (NEGs)](/load-balancing/docs/negs)**: how GKE Services use NEGs to integrate with Cloud Load Balancing.”