ノードプールとは、クラスタ内で同じ構成を持つノードのグループのことです。デフォルトでは、ハイブリッドはすべての 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。"],[[["\u003cp\u003eThis documentation outlines the minimum cluster configurations for Apigee hybrid version 1.7, which is currently end-of-life and should be upgraded.\u003c/p\u003e\n"],["\u003cp\u003eDedicated node pools for stateful (like Cassandra) and stateless components are recommended due to differing resource requirements, with specific minimum configurations outlined for each.\u003c/p\u003e\n"],["\u003cp\u003eThe minimum configurations for both stateful and stateless node pools include 3 nodes per region, 4 CPU cores, 15 RAM, and different default label names.\u003c/p\u003e\n"],["\u003cp\u003eFor production environments, a minimum of two clusters are recommended.\u003c/p\u003e\n"],["\u003cp\u003eCassandra requires a minimum of 1 Gbps network bandwidth (more for production) and synchronized time across all pods and regions to avoid data inconsistencies due to its reliance on the Gossip protocol and timestamp-based data synchronization.\u003c/p\u003e\n"]]],[],null,["# Minimum cluster configurations\n\n| You are currently viewing version 1.7 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).\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.7/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\n\nCassandra uses the\n[Gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol) to\nexchange information with other nodes about network topology.\n\n\nThe use of Gossip plus the distributed 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\n\nApigee recommends using instance type with a minimum 1 Gbps network bandwidth and more than 1 Gbps\nfor production systems.\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.7/cassandra-production)\n- [Scaling Cassandra pods](/apigee/docs/hybrid/v1.7/cassandra-scaling)\n- [Configuring dedicated node pools](/apigee/docs/hybrid/v1.7/configure-dedicated-nodes)\n- [Scale and autoscale runtime services](/apigee/docs/hybrid/v1.7/scale-and-autoscale)"]]
