이 주제에서는 Apigee Hybrid의 최소 클러스터 구성을 설명합니다. 이러한 최소 구성은 지원되는 모든 Kubernetes 플랫폼에 적용됩니다.
노드 풀 정보
노드 풀은 클러스터 내에서 구성이 모두 동일한 노드 그룹입니다. 기본적으로 하이브리드는 모든 pod를 기본 노드 풀에 할당합니다. 그러나 전용 노드 풀을 만들고 여기에 하이브리드 구성요소를 할당하여 리소스를 배포할 수 있습니다.
일반적으로 리소스 요구사항이 서로 다른 pod가 있는 경우 전용 노드 풀을 정의합니다. 예를 들어 apigee-cassandra pod에는 영구 스토리지가 필요하지만 다른 Apigee Hybrid pod에는 필요하지 않습니다. 따라서 Cassandra용 스테이트풀(Stateful) 노드 풀과 나머지 하이브리드 런타임 서비스용 스테이트리스(Stateless) 노드 풀을 만드는 것이 좋습니다. 자세한 내용은 전용 노드 풀 구성을 참조하세요.
다음 섹션에는 스테이트풀(Stateful) 및 스테이트리스(Stateless) 노드 풀의 구성이 모두 나와 있습니다.
[[["이해하기 쉬움","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-09-04(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)"]]
