Anda dapat menginstal Apigee hybrid di sejumlah platform, termasuk Google Distributed Cloud (di bare metal atau VMware), AWS, Bare Metal, EKS, Google Kubernetes Engine (GKE), OpenShift, dan lainnya. Untuk mengetahui daftar platform yang didukung,
lihat Apigee hybrid: platform yang didukung.
Izin
Setiap platform yang didukung memiliki persyaratan izinnya sendiri untuk membuat cluster. Sebagai pemilik
cluster, Anda dapat melanjutkan untuk menginstal komponen khusus Apigee (termasuk cert-manager dan
runtime Apigee) ke dalam cluster. Namun, jika ingin mendelegasikan penginstalan komponen runtime ke dalam cluster kepada pengguna lain, Anda dapat mengelola izin yang diperlukan melalui authn-authz Kubernetes.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-21 UTC."],[[["\u003cp\u003eApigee hybrid can be installed on various platforms, including Google Distributed Cloud, AWS, Bare Metal, EKS, GKE, and OpenShift, among others.\u003c/p\u003e\n"],["\u003cp\u003eEach platform has specific permission requirements for cluster creation, and cluster owners can manage permissions for runtime component installation via Kubernetes.\u003c/p\u003e\n"],["\u003cp\u003eBefore starting the runtime plane installation, users must complete the project and organization setup tasks as detailed in Part 1, including having a Google Cloud project, a billing account, and the \u003ccode\u003egcloud\u003c/code\u003e CLI installed.\u003c/p\u003e\n"],["\u003cp\u003ePrior to initiating the runtime setup, users must also enable the necessary APIs for Google Cloud services, and create both an Apigee organization, and an Apigee environment group.\u003c/p\u003e\n"]]],[],null,["# Part 2: Hybrid runtime setup\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nSupported platforms\n-------------------\n\n\nYou can install Apigee hybrid on a number of platforms, including Google Distributed Cloud (on bare metal or VMware), AWS, Bare Metal, EKS, Google Kubernetes Engine (GKE), OpenShift, and others. For a list of supported platforms\nsee [Apigee hybrid: supported platforms](/apigee/docs/hybrid/supported-platforms).\n\nPermissions\n-----------\n\n\nEach supported platform has its own permission requirements for creating a cluster. As cluster\nowner, you can proceed to install the Apigee-specific components (including cert-manager and the\nApigee runtime) into the cluster. However, if you want to delegate to another user the\ninstallation of the runtime components into the cluster, you can manage the necessary permissions\nthrough Kubernetes\n[authn-authz](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).\n\nFor a complete list of Kubernetes resources and custom resources that are used by Apigee installations,\nsee [Kubernetes and custom resources used by Apigee](../kubernetes-resources).\n\nPrerequisites\n-------------\n\nThis section describes tasks you must accomplish before you begin the runtime plane quickstart\ninstall.\n\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."]]
