O seu cluster tem de cumprir os requisitos mínimos de configuração. Para obter detalhes, consulte o artigo
Configurações mínimas do cluster.
Autorizações de cluster
Cada plataforma suportada tem os seus próprios requisitos de autorização para criar um cluster. Após a criação do cluster. Enquanto proprietário do cluster, pode proceder à instalação dos componentes específicos do Apigee
(incluindo o Apigee, o ASM e o cert-manager) no
cluster. No entanto, se quiser delegar a instalação dos componentes de tempo de execução a outro utilizador no cluster, pode gerir as autorizações necessárias através da autenticação/autorização do Kubernetes.
Para instalar os componentes do tempo de execução híbrido no cluster, um utilizador que não seja o proprietário do cluster deve ter autorização de criação, leitura, atualização e eliminação nestes recursos:
ClusterRole
Webhooks (ValidatingWebhookConfiguration e MutatingWebhookConfiguration)
PriorityClass
ClusterIssuer
CustomerResourceDefinitions
StorageClass (opcional, se não for usada a StorageClass predefinida)
Pré-requisitos
Esta secção descreve as tarefas que tem de concluir antes de iniciar a instalação
do guia de início rápido do plano de tempo de execução.
Conclua as seguintes tarefas para garantir que pode iniciar com êxito a instalação em tempo de execução (conforme descrito nesta secção):
Depois de cumprir os pré-requisitos acima, aceda ao guia de início rápido da sua plataforma:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-21 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:"]]
