클러스터는 최소 구성 요구사항을 충족해야 합니다. 자세한 내용은 최소 클러스터 구성을 참조하세요.
클러스터 권한
지원되는 각 플랫폼에는 클러스터를 만들기 위한 고유 권한 요구사항이 있습니다. 클러스터가 생성된 후에 클러스터 소유자는 계속해서 Apigee 관련 구성요소(Apigee, ASM, cert-manager 포함)를 클러스터에 설치할 수 있습니다. 하지만 다른 사용자에게 클러스터 내의 런타임 구성요소 설치를 위임하려는 경우 Kubernetes authn-authz를 통해 필요한 권한을 관리할 수 있습니다.
클러스터에 하이브리드 런타임 구성요소를 설치하려면 클러스터 소유자가 아닌 사용자에게 이러한 리소스에 대한 CRUD 권한이 있어야 합니다.
ClusterRole
웹훅(ValidatingWebhookConfiguration 및 MutatingWebhookConfiguration)
PriorityClass
ClusterIssuer
CustomerResourceDefinitions
StorageClass(기본 StorageClass를 사용하지 않는 경우 선택사항)
기본 요건
이 섹션에서는 런타임 영역 빠른 시작 설치를 시작하기 전에 수행해야 하는 태스크를 설명합니다.
(이 섹션에 설명된 대로) 런타임 설치를 성공적으로 시작할 수 있도록 다음 작업을 완료합니다.
[[["이해하기 쉬움","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-05(UTC)"],[[["\u003cp\u003eThis documentation covers version 1.3 of Apigee hybrid, which is now end-of-life, and users should upgrade to a newer version for continued support.\u003c/p\u003e\n"],["\u003cp\u003eClusters used for Apigee hybrid must meet specific minimum configuration requirements, detailed in the documentation.\u003c/p\u003e\n"],["\u003cp\u003eInstalling Apigee hybrid runtime components into the cluster requires non-cluster-owner users to have CRUD permission on specified resources like ClusterRole and Webhooks.\u003c/p\u003e\n"],["\u003cp\u003eBefore beginning the runtime installation, users must complete the Google Cloud and UI setup, and have a registered domain name.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid can be installed in either a shared cluster with other workloads or in a dedicated cluster, each option having different implications for management and potential version conflicts.\u003c/p\u003e\n"]]],[],null,["# Part 2: Runtime quickstart\n\n| You are currently viewing version 1.3 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\nSupported platforms\n-------------------\n\n\nSee [Apigee hybrid: supported platforms](/apigee/docs/hybrid/supported-platforms).\n\nMinimum cluster configurations\n------------------------------\n\n\nYour cluster must meet minimum configuration requirements. For details, see\n[Minimum cluster configurations](/apigee/docs/hybrid/v1.3/cluster-overview).\n\nCluster permissions\n-------------------\n\n\nEach supported platform has its own permission requirements for creating a cluster. After the cluster\nis created. As cluster owner, you can proceed to install the Apigee-specific components\n(including Apigee, ASM, and cert-manager) into\nthe cluster. However, if you want to delegate to another user the installation of the runtime\ncomponents into the cluster, you can manage the\nnecessary permissions through\nKubernetes [authn-authz](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).\n\n\nTo install the hybrid runtime components into the cluster, a non-cluster-owner user should\nhave CRUD permission on these resources:\n\n- ClusterRole\n- Webhooks (ValidatingWebhookConfiguration and MutatingWebhookConfiguration)\n- PriorityClass\n- ClusterIssuer\n- CustomerResourceDefinitions\n- StorageClass (optional, if the default StorageClass is not used)\n\nPrerequisites\n-------------\n\nThis section describes tasks you must accomplish before you begin the runtime plane quickstart\ninstall.\n\n| **Note about clusters:** You can create a new separate cluster for Apigee hybrid or you can install it in a cluster that is running other workloads. \n|\n| - **Shared cluster:** If you install Apigee hybrid in a cluster running other workloads, you need to upgrade and maintain your GKE/AKS cluster at the versions and features required in common for Apigee hybrid and for your other workloads. You may want to develop a plan to migrate one or more workloads in case conflicts arise between supported versions and requirements.\n| - **Separate cluster:** Creating a dedicated cluster for Apigee hybrid adds isolation. It also adds the operational effort of maintaining the new cluster.\n| Both options are valid.\n| **Note about VPC Service Controls:** If you plan to enable Google Cloud [Virtual Private Cloud (VPC) Service\n| Controls](https://cloud.google.com/vpc-service-controls) with your Apigee hybrid installation, see [Using VPC Service Controls with Apigee and\n| Apigee hybrid](/apigee/docs/api-platform/security/vpc-sc) for instructions before you proceed.\n\nAfter you have satisfied the above prerequisites, go to the quickstart for your platform:"]]
