节点池是集群中全都具有相同配置的一组节点。默认情况下，Hybrid 会将所有 pod 都分配给默认节点池；不过，您可以创建专用节点池，并采用分配资源的方式为其分配 Hybrid 组件。
通常，如果 pod 具有不同的资源要求，您可以定义专用节点池。例如，apigee-cassandra pod 需要永久性存储空间，而其他 Apigee Hybrid pod 则不需要。因此，我们建议您为 Cassandra 创建有状态节点池，为其余的 Hybrid 运行时服务创建无状态节点池。如需了解详情，请参阅配置专用节点池。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-03。"],[[["\u003cp\u003eThis documentation outlines the minimum cluster configurations for non-production Apigee hybrid installations, applicable across all supported Kubernetes platforms.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid utilizes node pools, and it's recommended to create dedicated node pools: a stateful pool for Cassandra and a stateless pool for other runtime services.\u003c/p\u003e\n"],["\u003cp\u003eThe minimum configurations include one node per zone (three per region) for both stateful and stateless node pools, each with 4 CPUs, 15 RAM, and a minimum disk IOPS of 2000, while the storage of stateless nodes is managed by ApigeeDeployment CRD.\u003c/p\u003e\n"],["\u003cp\u003eCassandra requires a minimum of 1 Gbps network bandwidth, and for production environments, three availability zones are essential to maintain availability.\u003c/p\u003e\n"],["\u003cp\u003eEnsuring that time is synchronized across all pods and regions within the Cassandra cluster is crucial for consistent data synchronization.\u003c/p\u003e\n"]]],[],null,["# Minimum cluster configurations\n\n| You are currently viewing version 1.9 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.9/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\n\nCassandra clusters need three availability zones to maintain availability in a\nproduction environment. If one zone goes down, the remaining zones will\ncontinue responding to requests while the remaining zone comes back online. If\ntwo or more zones go down, Cassandra will be unable to respond to requests\nuntil at least two zones come back online. Apigee recommends bringing zones\nback online within three hours to minimize the risk of missing data\nupdates.\n\n\nWhen deploying multi-region hybrid environments, Apigee recommends using a VPN\nor cloud solution like\n[Google Cloud VPN](/network-connectivity/docs/vpn/concepts/overview) to secure connectivity between the\nregions. Make sure there are no overlapping subnets as these may cause\nCassandra connectivity issues. Ensure the current firewall configurations\nallow for Cassandra traffic to pass between Cassandra pods. See\n[Secure ports usage](/apigee/docs/hybrid/v1.9/ports) for information on Cassandra ports.\n\n\nThe maximum or 99th percentile latency for Cassandra should be below 100 milliseconds.\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.9/cassandra-production)\n- [Scaling Cassandra pods](/apigee/docs/hybrid/v1.9/cassandra-scaling)\n- [Configuring dedicated node pools](/apigee/docs/hybrid/v1.9/configure-dedicated-nodes)\n- [Scale and autoscale runtime services](/apigee/docs/hybrid/v1.9/scale-and-autoscale)"]]
