ノードプールとは、クラスタ内で同じ構成を持つノードのグループのことです。デフォルトでは、ハイブリッドの Pod はすべてデフォルトのノードプールに割り当てられますが、専用のノードプールを作成してハイブリッド コンポーネントを割り当てることによってリソースを分散させることもできます。
通常、リソース要件が異なる Pod がある場合は、専用のノードプールを定義します。たとえば、apigee-cassandra Pod には永続ストレージが必要ですが、他の Apigee ハイブリッド Pod には必要ありません。このため、Cassandra 用のステートフル ノードプールと、残りのハイブリッド ランタイム サービス用のステートレス ノードプールを作成することをおすすめします。詳細については、専用ノードプールを構成するをご覧ください。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-30 UTC。"],[],[],null,["# Minimum cluster configurations\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.15/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.15/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.15/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\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.15/cassandra-production)\n- [Scaling Cassandra pods](/apigee/docs/hybrid/v1.15/cassandra-scaling)\n- [Configuring dedicated node pools](/apigee/docs/hybrid/v1.15/configure-dedicated-nodes)\n- [Scale and autoscale runtime services](/apigee/docs/hybrid/v1.15/scale-and-autoscale)\n- [Multi-region deployments](/apigee/docs/hybrid/v1.15/multi-region)"]]
