Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Google Distributed Cloud mendukung dua opsi load balancer: paket dan manual.
Mode load balancer yang dipaketkan
Jika Anda memilih load balancing yang dipaketkan, load balancer akan disediakan untuk Anda. Load balancer eksternal tidak diperlukan.
Ada dua jenis load balancing yang dipaketkan:
Lapisan 2: Semua node load balancer dan VIP harus berada di subnet
Lapisan 2 yang sama. Gateway subnet load balancer harus memproses pesan ARP
serampangan dan meneruskan paket ARP ke node load balancer. Lihat
Load balancing yang dipaketkan dengan MetalLB.
BGP: Mode load balancing ini mendukung iklan alamat IP virtual (VIP)
ServiceType LoadBalancer melalui Border Gateway Protocol (eBGP) eksternal untuk cluster Anda. Jaringan cluster Anda adalah sistem
otonom, yang saling terhubung dengan sistem otonom lain, jaringan eksternal,
melalui peering. Lihat
Load balancing yang dipaketkan dengan BGP.
Diagram berikut menunjukkan contoh topologi jaringan tempat load balancer MetalLB
yang dipaketkan berada di node bidang kontrol.
Mode load balancer manual
Jika Anda memilih load balancing manual, Google Distributed Cloud tidak akan men-deploy load
balancer. Hal ini memungkinkan fleksibilitas yang lebih besar daripada load balancing yang dipaketkan dan tidak ada persyaratan jaringan L2.
Anda harus mengonfigurasi VIP node bidang kontrol di load balancer
eksternal sebelum menginstal cluster. Setelah penginstalan, Anda harus memilih solusi load
balancing untuk Layanan dan Ingress Kubernetes.
Diagram berikut menunjukkan contoh topologi jaringan cluster yang menggunakan
mode load balancing manual dengan load balancer eksternal.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-31 UTC."],[],[],null,["Google Distributed Cloud supports two load balancer options: bundled and manual.\n\nBundled load balancer mode\n\nIf you choose bundled load balancing, the load balancer is provided for you. An\nexternal load balancer is not needed.\n\nThere are two types of bundled load balancing:\n\n- **Layer 2** : All load balancer nodes and VIPs must be in the same Layer 2\n subnet. The gateway of the load balancer subnet must listen to gratuitous ARP\n messages and forward ARP packets to the load balancer nodes. See\n [Bundled load balancing with MetalLB](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/bundled-lb).\n\n- **BGP** : This load-balancing mode supports the advertisement of ServiceType\n LoadBalancer virtual IP addresses (VIPs) through external Border\n Gateway Protocol (eBGP) for your clusters. Your cluster network is an autonomous\n system, which interconnects with another autonomous system, an external network,\n through peering. See\n [Bundled load balancing with BGP](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/lb-bundled-bgp).\n\nThe following diagram shows an example network topology where bundled MetalLB\nload balancers are located on the control plane nodes.\n\nManual load balancer mode\n\nIf you choose manual load balancing, Google Distributed Cloud does not deploy load\nbalancers. This allows more flexibility than bundled load balancing and there\nare no L2 network requirements.\n\nYou must configure your control plane nodes' VIPs on an external load\nbalancer before installing the cluster. After installation, you must pick a load\nbalancing solution for Kubernetes Services and Ingresses.\n\nThe following diagram shows an example network topology of a cluster using\nmanual load balancing mode with an external load balancer."]]
