Ogni piattaforma supportata ha i propri requisiti di autorizzazione per la creazione di un cluster. Dopo aver creato il cluster. In qualità di proprietario del cluster, puoi procedere con l'installazione dei componenti specifici di Apigee (inclusi Apigee, ASM e cert-manager) nel cluster. Tuttavia, se vuoi delegare a un altro utente l'installazione dei componenti di runtime nel cluster, puoi gestire le autorizzazioni necessarie tramite authn-authz di Kubernetes.
Per installare i componenti di runtime ibrida nel cluster, un utente diverso dal proprietario del cluster deve disporre dell'autorizzazione CRUD per queste risorse:
ClusterRole
Webhook (ValidatingWebhookConfiguration e MutatingWebhookConfiguration)
PriorityClass
ClusterIssuer
CustomerResourceDefinitions
StorageClass (facoltativo, se non viene utilizzata la classe di archiviazione predefinita)
Prerequisiti
Questa sezione descrive le attività che devi svolgere prima di iniziare l'installazione guidata del piano di runtime.
Completa le seguenti attività per assicurarti di poter iniziare correttamente l'installazione del runtime (come descritto in questa sezione):
Dopo aver soddisfatto i prerequisiti sopra indicati, vai alla guida rapida per la tua piattaforma:
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-09 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:"]]