Topik ini menjelaskan konfigurasi cluster minimum untuk
Apigee Hybrid. Konfigurasi minimum ini berlaku untuk semua platform Kubernetes yang didukung. Rekomendasi dalam topik ini berlaku untuk penginstalan non-produksi, seperti skenario uji coba atau pengujian. Perhatikan rekomendasi ini saat melakukan langkah-langkah penginstalan Apigee Hybrid.
Tentang node pool
Node pool adalah sekelompok node dalam cluster yang semuanya memiliki konfigurasi yang sama. Secara default, hybrid menetapkan semua pod ke node pool default; namun, Anda dapat membuat node pool khusus dan menetapkan komponen hybrid ke node pool tersebut sebagai cara mendistribusikan resource.
Biasanya, Anda menentukan kumpulan node khusus saat memiliki pod dengan persyaratan resource
yang berbeda. Misalnya, pod apigee-cassandra memerlukan penyimpanan persisten, sedangkan
pod hybrid Apigee lainnya tidak. Oleh karena itu, sebaiknya Anda membuat
node pool stateful untuk Cassandra dan node pool stateless untuk layanan runtime
hibrida lainnya. Lihat Mengonfigurasi node pool khusus untuk mengetahui detailnya.
Bagian berikut mencantumkan konfigurasi untuk node pool stateful dan stateless.
Konfigurasi minimum
Gunakan konfigurasi minimum ini saat menyiapkan cluster:
Konfigurasi
Node pool stateful
Node pool stateless
Tujuan
Node pool stateful yang digunakan untuk database Cassandra.
Node pool stateless yang digunakan oleh pemroses pesan runtime.
2.000 IOPS dengan SAN atau penyimpanan terpasang langsung. NFS tidak direkomendasikan meskipun dapat mendukung IOPS yang diperlukan.
2.000 IOPS dengan SAN atau penyimpanan terpasang langsung. NFS tidak direkomendasikan meskipun dapat mendukung IOPS yang diperlukan.
Bandwidth jaringan untuk setiap jenis instance mesin
1 Gbps
1 Gbps
Persyaratan jaringan Cassandra
Bagian ini membahas persyaratan dan rekomendasi jaringan yang harus diikuti saat menyiapkan
Apigee Hybrid.
Bandwidth jaringan
Cassandra menggunakan
protokol Gossip untuk
bertukar informasi dengan node lain tentang topologi jaringan. Penggunaan Gossip ditambah dengan
sifat terdistribusi Cassandra—yang melibatkan komunikasi dengan beberapa
node untuk operasi baca dan tulis—menghasilkan banyak transfer data melalui jaringan.
Cassandra memerlukan bandwidth jaringan minimum 1 Gbps untuk setiap instance mesin. Misalnya,
di GKE, jenis mesin minimum yang direkomendasikan, e2-standard-4, memiliki bandwidth minimum
1 Gbps. Untuk penginstalan produksi, sebaiknya gunakan Gbps yang lebih tinggi.
Latensi maksimum atau persentil ke-99 untuk Cassandra harus di bawah 100 milidetik.
Mengamankan konektivitas jaringan antar-region
Saat menginstal hybrid di beberapa region, pastikan koneksi antar-region
aman:
Gunakan solusi virtual private network, seperti Virtual Private Cloud (VPC) Google,
untuk mengamankan konektivitas antar-region.
Buka firewall untuk memastikan node Cassandra dapat terhubung antar-region dalam subnet yang tidak tumpang-tindih dan dapat me-resolve
IP jaringan tersebut.
Selalu gunakan port 7001 untuk Cassandra.
Semua port lainnya bersifat lokal untuk region tersebut.
Lihat juga Penggunaan port aman.
Persyaratan NTP Cassandra
Data Cassandra disinkronkan berdasarkan stempel waktu sistem. Pastikan waktu
disinkronkan di semua pod dan semua region dalam cluster Cassandra. Penundaan waktu
antara node dan region menyebabkan inkonsistensi data.
Menskalakan konfigurasi
Jika Anda perlu menskalakan konfigurasi awal berdasarkan kebutuhan kapasitas atau throughput tambahan,
lihat topik berikut:
[[["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-09-04 UTC."],[[["\u003cp\u003eThis documentation outlines the minimum cluster configurations for non-production Apigee hybrid installations across supported Kubernetes platforms, including trial and testing scenarios.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid uses node pools, which are groups of nodes within a cluster with identical configurations, and it is recommended to have a dedicated stateful node pool for Cassandra and a stateless one for other runtime services.\u003c/p\u003e\n"],["\u003cp\u003eBoth stateful (Cassandra) and stateless node pools require a minimum of 1 node per zone, 4 CPU, 15 RAM, and 2000 IOPS storage with at least 1 Gbps network bandwidth.\u003c/p\u003e\n"],["\u003cp\u003eFor multi-region deployments, secure network connectivity between regions is crucial, utilizing solutions like Virtual Private Networks, firewalls to open connections between regions, and ensuring consistent time synchronization across Cassandra pods.\u003c/p\u003e\n"],["\u003cp\u003eIf scaling is needed, there are several links provided, for resources such as configuring Cassandra for production, scaling pods, creating dedicated node pools, scaling runtime services, or using a multi-region setup.\u003c/p\u003e\n"]]],[],null,["# Minimum cluster configurations\n\n| You are currently viewing version 1.11 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis topic describes minimum cluster configurations for\nApigee hybrid. These minimum configurations apply to all of the supported\n[Kubernetes platforms](/apigee/docs/hybrid/supported-platforms). The recommendations\nin this topic apply for non-production installations, such as trial or testing scenarios. Keep\nthese recommendations in mind when performing the Apigee hybrid installation steps.\n\nAbout node pools\n----------------\n\n\nA node pool is a group of nodes within a cluster that all have the same configuration. By\ndefault, hybrid assigns all pods to the default node pool; however, you can create dedicated\nnode pools and assign hybrid components to them as a way of distributing resources.\n\n\nTypically, you define dedicated node pools when you have pods with differing resource\nrequirements. For example, the `apigee-cassandra` pods require persistent storage, while\nthe other Apigee hybrid pods do not. For this reason, we recommend that you create\na stateful node pool for Cassandra and a stateless node pool for the rest of the hybrid\nruntime services. See [Configure dedicated node pools](/apigee/docs/hybrid/v1.11/configure-dedicated-nodes) for\ndetails.\n\n\nThe following section lists configurations for both stateful and stateless node pools.\n\nMinimum configurations\n----------------------\n\n\nUse these minimum configurations when setting up your cluster:\n\n| **Note:** For **production** environments, we recommend a minimum of two clusters.\n\nCassandra network requirements\n------------------------------\n\nThis section discusses network requirements and recommendations to follow when setting up\nApigee hybrid.\n\n### Network bandwidth\n\n\nCassandra uses the\n[Gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol) to\nexchange information with other nodes about network topology. The use of Gossip plus the\ndistributed nature of Cassandra---which involves talking to multiple\nnodes for read and write operations---results in a lot of data transfer through the network.\n\nCassandra requires a minimum of 1 Gbps of network bandwidth for each machine instance. For example,\non GKE, the minimum recommended machine type, `e2-standard-4`, has a minimum bandwidth\nof 1 Gbps. For production installations, a higher Gbps is recommended.\n\nThe maximum or 99th percentile latency for Cassandra should be below 100 milliseconds.\n\n### Secure network connectivity between regions\n\nWhen installing hybrid in [multiple regions](/apigee/docs/hybrid/v1.11/multi-region), ensure that the connections between\nregions is secure:\n\n- Use a virtual private network solution, such as Google [Virtual Private Cloud](/vpc/docs/overview) (VPC), to secure connectivity between regions.\n- Open a firewall to ensure that Cassandra nodes can connect between regions in non-overlapping subnets and can resolve those network IPs.\n- Always use port 7001 for Cassandra. All other ports are local to the region. See also [Secure ports usage](/apigee/docs/hybrid/v1.11/ports).\n\nCassandra NTP requirements\n--------------------------\n\n\nCassandra data synchronizes based on the timestamp of the system. Ensure that the time is\nsynchronized across all pods and all regions within the Cassandra cluster. Time delays\nbetween the nodes and regions causes data inconsistencies.\n| **Tip:** If firweall is used, try setting up the TCP keepalive settings for the stateful nodes similar to the following: \n|\n| ```\n| net.ipv4.tcp_keepalive_time=60\n| net.ipv4.tcp_keepalive_probes=3\n| net.ipv4.tcp_keepalive_intvl=10\n| \n| ```\n| This could help prevent a firewall from considering the connections idle and dropping them. TCP settings in the datastax documentation.\n\nScaling the configuration\n-------------------------\n\n\nIf you need to scale your initial configuration based on additional capacity or throughput needs,\nsee the following topics:\n\n- [Configuring Cassandra for production](/apigee/docs/hybrid/v1.11/cassandra-production)\n- [Scaling Cassandra pods](/apigee/docs/hybrid/v1.11/cassandra-scaling)\n- [Configuring dedicated node pools](/apigee/docs/hybrid/v1.11/configure-dedicated-nodes)\n- [Scale and autoscale runtime services](/apigee/docs/hybrid/v1.11/scale-and-autoscale)\n- [Multi-region deployments](/apigee/docs/hybrid/v1.11/multi-region)"]]
