Platform F5 BIG-IP menyediakan
berbagai layanan untuk membantu Anda meningkatkan keamanan, ketersediaan, dan performa
aplikasi. Layanan ini mencakup load balancing L7, firewall jaringan,
firewall aplikasi web
(WAF),
layanan DNS, dan lainnya. Untuk Google Distributed Cloud, BIG-IP menyediakan
akses eksternal dan layanan load balancing L3/4.
Konfigurasi tambahan
Setelah utilitas Penyiapan selesai,
Anda perlu Membuat partisi administratif
untuk setiap cluster pengguna yang ingin Anda ekspos dan akses.
Awalnya, Anda menentukan partisi
untuk cluster pengguna pertama. Jangan gunakan partisi cluster untuk hal lain.
Setiap cluster harus memiliki partisi yang hanya digunakan untuk cluster tersebut.
Mengonfigurasi BIG-IP untuk endpoint eksternal Google Distributed Cloud
VIP untuk pengontrol ingress cluster pengguna (port yang diekspos: 443)
VIP untuk pengontrol ingress cluster pengguna (port yang diekspos: 80)
Membuat objek node
Alamat IP eksternal node cluster pada gilirannya digunakan untuk mengonfigurasi objek node di sistem BIG-IP. Anda akan membuat objek node untuk setiap node cluster Google Distributed Cloud. Node ditambahkan ke kumpulan backend yang kemudian dikaitkan dengan
server virtual.
Untuk login ke konsol pengelolaan BIG-IP, buka alamat IP. Alamat
diberikan selama penginstalan.
Klik Partisi pengguna yang sebelumnya Anda buat.
Buka Traffic Lokal > Node > Daftar Node.
Klik Buat.
Masukkan nama dan alamat IP untuk setiap host cluster, lalu klik Selesai.
Membuat kumpulan backend
Anda membuat kumpulan backend untuk setiap Port node.
Di konsol pengelolaan BIG-IP, klik Partisi pengguna untuk partisi pengguna
yang sebelumnya Anda buat.
Buka Traffic Lokal > Pembagian > Daftar Pembagian.
Klik Buat.
Di menu drop-down Konfigurasi, klik Lanjutan.
Di kolom Name, masukkan Istio-80-pool.
Untuk memverifikasi aksesibilitas anggota kumpulan, di bagian Health Monitor, klik
tcp. Opsional: Karena ini adalah konfigurasi manual, Anda juga dapat
memanfaatkan lebih banyak
pemantau lanjutan
sesuai dengan deployment Anda.
Untuk Tindakan jika Layanan Tidak Ada, klik Tolak.
Untuk tutorial ini, di menu drop-down Load Balancing Method,
klik Round Robin.
Di bagian New Members, klik Node List, lalu pilih node yang dibuat sebelumnya.
Di kolom Service Port, masukkan nodePort yang sesuai dari file konfigurasi atau spec.ports[?].nodePort di Layanan Kubernetes istio ingress runtime (nama: istio-ingress, namespace: gke-system).
Klik Tambahkan.
Ulangi langkah 8-9 dan tambahkan setiap instance node cluster.
Anda membuat total dua server virtual di BIG-IP untuk cluster pengguna pertama. Server virtual sesuai dengan
kombinasi "VIP + port".
Di konsol pengelolaan BIG-IP, klik Partisi pengguna yang
Anda buat sebelumnya.
Buka Traffic Lokal > Server Virtual > Daftar Server Virtual.
Klik Buat.
Di kolom Name, masukkan istio-ingress-80.
Di kolom Destination Address/Mask, masukkan alamat IP untuk VIP. Untuk tutorial ini, gunakan VIP ingress HTTP di
configuration file atau spec.loadBalancerIP di Layanan Kubernetes
ingress istio runtime (nama: istio-ingress, namespace: gke-system).
Di kolom Service Port, masukkan port pemroses yang sesuai untuk VIP. Untuk tutorial ini, gunakan port 80 atau spec.ports[?].port di Layanan Kubernetes istio ingress runtime (nama: istio-ingress, namespace: gke-system).
Ada beberapa opsi konfigurasi untuk meningkatkan endpoint aplikasi Anda,
seperti mengaitkan profil khusus protokol,
profil sertifikat,
dan
kebijakan WAF.
Untuk Penafsiran Alamat Sumber, klik Peta Otomatis.
Untuk Default Pool, pilih kumpulan yang sesuai yang sebelumnya Anda buat.
[[["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-22 UTC."],[],[],null,["This tutorial shows how to set up the\n[F5 BIG-IP](https://www.f5.com/products/big-ip-services) when\nyou [integrate with Google Distributed Cloud](/kubernetes-engine/distributed-cloud/vmware/docs)\nusing the\n[manual load-balancing mode on Google Distributed Cloud](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/manual-load-balance).\n\nThe F5 BIG-IP platform provides\nvarious services to help you enhance the security, availability, and performance\nof your apps. These services include, L7 load balancing, network firewalling,\n[web application firewalling\n(WAF)](https://wikipedia.org/wiki/Web_application_firewall),\nDNS services, and more. For Google Distributed Cloud, BIG-IP provides\nexternal access and L3/4 load-balancing services.\n\nAdditional configuration\n\nAfter the Setup utility completes,\nyou need to [Create an administrative partition](https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-user-account-administration-12-0-0/3.html)\nfor each user cluster you intend to expose and access.\n\nInitially, you define a partition\nfor the first user cluster. Don't use cluster partitions for anything else.\nEach of the clusters must have a partition that is for the sole use of that\ncluster.\n\nConfiguring the BIG-IP for Google Distributed Cloud external endpoints\n\nIf you didn't [disable bundled ingress](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/disable-bundled-ingress), you must\n[configure the BIG-IP with the virtual servers](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/manual-load-balance#cp-v2-user-cluster_4)\n(VIPs), corresponding to the following Google Distributed Cloud endpoints:\n\n- **User partition**\n\n - VIP for user cluster ingress controller (port exposed: `443`)\n - VIP for user cluster ingress controller (port exposed: `80`)\n\n| **Note:** Because Google Distributed Cloud blocks creating clusters with [legacy features](/kubernetes-engine/distributed-cloud/vmware/docs/concepts/migrate-recommended-features), this document doesn't cover the BIG-IP configuration for legacy features.\n\nCreate node object\n\nThe cluster node external IP addresses are in turn used to configure node objects on the BIG-IP\nsystem. You will create a node object for each Google Distributed Cloud\ncluster node. The nodes are added to backend pools that are then associated with\nvirtual servers.\n| **Important:** If you choose [DHCP IP Mode](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest#network-ipmode-type-field), you need to update IP addresses for each node object on the BIG-IP system once the Google Distributed Cloud cluster node IP addresses changed.\n\n1. To sign in to the BIG-IP management console, go to the IP address. The address is provided during the installation.\n2. Click the **User partition** that you previously created.\n3. Go to **Local Traffic** \\\u003e **Nodes** \\\u003e **Node List**.\n4. Click **Create**.\n5. Enter a name and IP address for each cluster host and click **Finished**.\n\nCreate backend pools\n\nYou create a backend pool for each node Port.\n\n1. In the BIG-IP management console, click **User partition** for the user partition that you previously created.\n2. Go to **Local Traffic** \\\u003e **Pools** \\\u003e **Pool List**.\n3. Click **Create**.\n4. In the **Configuration** drop-down list, click **Advanced**.\n5. In the **Name** field, enter `Istio-80-pool`.\n6. To verify the pool member accessibility, under **Health Monitor** , click **tcp** . Optional: Because this is a manual configuration, you can also take advantage of more [advanced monitors](https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-local-traffic-manager-monitors-reference-13-1-0.html) as appropriate for your deployment.\n7. For **Action on Service Down** , click **Reject**.\n\n8. For this tutorial, in the **Load Balancing Method** drop-down list,\n click **Round Robin**.\n\n9. In the **New Members** section, click **Node List** and then select the\n previously created node.\n\n10. In the **Service Port** field, enter the appropriate `nodePort` from the\n [configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/manual-load-balance#cp-v2-user-cluster_2) or `spec.ports[?].nodePort` in the runtime\n istio ingress Kubernetes Service (name: `istio-ingress`, namespace: `gke-system`).\n\n11. Click **Add**.\n\n12. Repeat steps 8-9 and add each cluster node instance.\n\n13. Click **Finished**.\n\n14. Repeat all of these steps in this section for the remaining\n [user cluster nodePorts](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/manual-load-balance#cp-v2-user-cluster_4).\n\nCreate virtual servers\n\nYou create a total of two virtual servers on the BIG-IP for the first user cluster. The virtual servers correspond to\nthe \"VIP + port\" combinations.\n\n1. In the BIG-IP management console, click the **User partition** that you previously created.\n2. Go to **Local Traffic** \\\u003e **Virtual Servers** \\\u003e **Virtual Server List**.\n3. Click **Create**.\n4. In the **Name** field, enter `istio-ingress-80`.\n5. In the **Destination Address/Mask** field, enter the IP address for the\n VIP. For this tutorial, use the HTTP ingress VIP in the\n [`configuration file`](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/manual-load-balance#cp-v2-user-cluster_1) or `spec.loadBalancerIP` in the runtime\n istio ingress Kubernetes Service (name: `istio-ingress`, namespace: `gke-system`).\n\n | **Warning:** Don't setup a virtual server for `controlPlaneVIP`.\n6. In the **Service Port** field, enter the appropriate listener port for\n the VIP. For this tutorial, use port `80` or `spec.ports[?].port` in the runtime\n istio ingress Kubernetes Service (name: `istio-ingress`, namespace: `gke-system`).\n\n There are several configuration options for enhancing your app's endpoint,\n such as associating protocol-specific profiles,\n [certificate profiles](https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-profiles-reference-13-1-0/6.html#guid-cc146765-9237-474b-9faf-0e18a208cb23),\n and\n [WAF policies](https://support.f5.com/csp/article/K85426947).\n7. For **Source Address Translation** click **Auto Map**.\n\n8. For **Default Pool** select the appropriate pool that you previously\n created.\n\n9. Click **Finished**.\n\n10. [Create and download an archive of the current configuration](https://support.f5.com/csp/article/K4423).\n\nWhat's next\n\n- To further enhance the security and performance of the external-facing\n VIPs, consider the following:\n\n - [F5 Advanced WAF](https://www.f5.com/products/security/advanced-waf)\n - [F5 Access Policy Manager (APM)](https://www.f5.com/products/security/access-policy-manager)\n - [Caching \\& Compression](https://www.f5.com/products/big-ip-services/local-traffic-manager)\n - [Health monitoring](https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-local-traffic-manager-implementations/implementing-health-and-performance-monitoring.html)\n - [Intelligent application traffic management](https://www.f5.com/products/big-ip-services/local-traffic-manager)\n- Learn more about F5\n [BIG-IP Application Services](https://www.f5.com/products/big-ip-services).\n\n- Learn more about BIG-IP configurations and capabilities:\n\n - [Certificate profiles](https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-profiles-reference-13-1-0/6.html#guid-cc146765-9237-474b-9faf-0e18a208cb23)\n - [WAF policies](https://support.f5.com/csp/article/K85426947)"]]
