As novas organizações híbridas do Apigee podem ser aprovisionadas com a capacidade de implementar mais de 50 proxies por ambiente. Esta funcionalidade também está disponível para o Apigee X.
O número máximo de proxies de API implementados e fluxos partilhados por organização é de 6000.
O número máximo de unidades de implementação de proxy por instância do Apigee é de 6000.
O número máximo de caminhos base da API por organização do Apigee é de 3000.
Quando são implementados mais de 50 proxies num ambiente, o Apigee divide automaticamente o ambiente em vários conjuntos de réplicas distintos, cada um contendo um subconjunto de proxies implementados no ambiente. Estes subconjuntos de réplicas são equivalentes em termos de comportamento a um único ambiente na forma como carregam e executam um conjunto de proxies e outros recursos do ambiente. Isto é transparente para o utilizador, e pode continuar a usar o ambiente como se fosse um único ambiente.
A aprovisionar
Para aprovisionar uma nova organização com o número melhorado de proxies por ambiente:
Indique o ID do projeto e o nome da organização ao seu representante da Apigee para configurar o limite de proxy melhorado.
Siga as instruções de instalação do Apigee hybrid para aprovisionar a organização híbrida. No ficheiro de substituições, adicione a propriedade de nível superior enhanceProxyLimits:
enhanceProxyLimits: true
Aplique alterações a enhanceProxyLimits atualizando o gráfico apigee-org e o gráfico apigee-virtualhost para cada grupo de ambientes.
Crie e implemente um proxy.
Verifique se os limites de proxy melhorados estão ativados:
Obtenha o nome do configmap para o seu espaço de nomes do Apigee:
kubectl get configmap -n APIGEE_NAMESPACE
O resultado deve ser semelhante ao seguinte:
NAME DATA AGE
...
apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a 3 12m
...
Verifique o configmap com nome:
kubectl get configmap -n APIGEE_NAMESPACECONFIGMAP_NAME -o yaml
Em que CONFIGMAP_NAME é o nome do configmap do passo anterior.
Verifique a existência de pods de tempo de execução que contenham a substring auto:
kubectl get pods -n APIGEE_NAMESPACE | grep auto
O resultado deve ser semelhante ao seguinte:
kubectl get pods -n apigee | grep auto
apigee-runtime-hybr-test-env-auto-2ecde5a-bca5298-4gsrw 1/1 Running 0 98m
Limitações
O Apigee oferece limites de proxy por ambiente melhorados apenas em organizações criadas recentemente. A conversão de organizações existentes para usar limites de proxy melhorados não é suportada.
Não é possível restaurar cópias de segurança de uma organização criada sem limites de proxy melhorados para uma organização criada com a funcionalidade ativada.
[[["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\u003eNew Apigee hybrid organizations can now be provisioned to deploy more than 50 proxies per environment, a feature also available for Apigee X, and is subject to the 2024 subscription plan entitlements.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the enhanced proxy limit requires setting the \u003ccode\u003eenhanceProxyLimits\u003c/code\u003e property to \u003ccode\u003etrue\u003c/code\u003e in the overrides file during the provisioning of a new organization and this setting cannot be changed once set.\u003c/p\u003e\n"],["\u003cp\u003eWhen over 50 proxies are deployed, Apigee automatically partitions the environment into replica sets, which is transparent to the user and does not change how the environment is used.\u003c/p\u003e\n"],["\u003cp\u003eEnhanced proxy limits are only available for new organizations and not for existing ones, and backups of orgs created without it cannot be restored to organizations created with it enabled.\u003c/p\u003e\n"],["\u003cp\u003eProxy chaining with mTLS is not supported, and there might be virtual host conflicts during Helm release creation, which requires manual annotation commands to resolve.\u003c/p\u003e\n"]]],[],null,["# Enhanced per-environment proxy limits\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nOverview\n--------\n\n\nNew Apigee hybrid organizations can be provisioned with the ability to deploy more than 50 proxies per environment enabled. This feature is also available for [Apigee X](/apigee/docs/api-platform/reference/limits#api-proxies).\n\n- The maximum number of deployed API proxies and shared flows per organization is 6000.\n- The maximum number of proxy deployment units per Apigee instance is 6000.\n- The maximum number of API base paths per Apigee organization is 3000.\n\n\nWhen more than 50 proxies are deployed in an environment, Apigee will automatically partition the environment into several distinct replica sets, each containing a subset of proxies deployed in the environment. These replica subsets are equivalent in behavior to a single environment in the way it loads and runs a set of proxies and other environment resources. This will be transparent to the user, and you can continue to use the environment as you would a single environment.\n| **Note:** Enhanced proxy limits feature is only available for new hybrid organizations. This feature is available exclusively as part of the [2024 subscription plan](https://cloud.google.com/apigee/docs/api-platform/reference/subscription-entitlements#subscription-2024-entitlements), and is subject to the entitlements granted under that subscription. They cannot be enabled on existing organizations.\n\nProvisioning\n------------\n\n\nTo provision a new org with the enhanced number of proxies per environment:\n\n1. Provide your project ID and organization name to your Apigee representative to set up the enhanced proxy limit.\n2. Follow the Apigee hybrid [installation instructions](/apigee/docs/hybrid/v1.14/install-before-begin) to provision the hybrid org. In your overrides file, add the [`enhanceProxyLimits`](/apigee/docs/hybrid/v1.14/config-prop-ref#enhanceproxylimits) top-level property: \n\n ```\n enhanceProxyLimits: true\n ```\n\n Apply changes to `enhanceProxyLimits` by updating the `apigee-org` chart and the `apigee-virtualhost` chart for every environment group.\n | **Alert:** Do not change this value once set.\n3. Create and deploy a proxy.\n4. Verify that the enhanced proxy limits are enabled:\n 1. Get the name of the configmap for your Apigee namespace: \n\n ```\n kubectl get configmap -n APIGEE_NAMESPACE\n ```\n\n\n Your output should look similar to the following: \n\n ```\n NAME DATA AGE\n ...\n apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a 3 12m\n ...\n ```\n 2. Check the named configmap: \n\n ```\n kubectl get configmap -n APIGEE_NAMESPACE CONFIGMAP_NAME -o yaml\n ```\n\n\n Where \u003cvar translate=\"no\"\u003eCONFIGMAP_NAME\u003c/var\u003e is the name of the configmap from the previous step.\n\n\n Your output should look similar to the following: \n\n kubectl get configmap -n apigee apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a -o yaml\n apiVersion: v1\n data:\n contract.revid: \"2\"\n contract.uid: 4a792429-20fb-4b29-bed3-3f8ce7b3353e\n deploymentGroups: auto-2ecde5ae-04\n kind: ConfigMap\n metadata:\n creationTimestamp: \"2024-05-15T20:04:26Z\"\n labels:\n apigee.cloud.google.com/platform: apigee\n name: apigee-synchronizer-hybr-test-env-dggroupconfi-bc7726a\n namespace: apigee\n ownerReferences:\n - apiVersion: apigee.cloud.google.com/v1alpha2\n blockOwnerDeletion: true\n controller: true\n kind: ApigeeEnvironment\n name: hybrid-dev--test-env-4f37f70\n uid: 696e84ec-5c54-4858-a2e0-e36db5ff3506\n resourceVersion: \"2520100\"\n uid: b297bd33-300a-48cf-bf85-6c7cd0ff288f\n\n5. Check for the existence of runtime pods containing the substring `auto`: \n\n ```\n kubectl get pods -n APIGEE_NAMESPACE | grep auto\n ```\n\n\n Your output should look similar to the following: \n\n kubectl get pods -n apigee | grep auto\n apigee-runtime-hybr-test-env-auto-2ecde5a-bca5298-4gsrw 1/1 Running 0 98m\n\nLimitations\n-----------\n\n\nApigee offers enhanced per-environment proxy limits only on newly created orgs. Converting existing orgs to use enhanced proxy limits is not supported.\n\n\nBackups of an organization that was created without enhanced proxy limits enabled cannot be restored to an organization created with the feature enabled.\n\nKnown issues\n------------\n\n- Proxy chaining:\n - Proxy chaining with mTLS is not supported. See [known issue 392135466](/apigee/docs/release/known-issues#392135466).\n\nTroubleshooting\n---------------"]]
