Overview

New Apigee hybrid organizations can be provisioned with the ability to deploy more than 50 proxies per environment enabled. This feature is also available forApigee X.

• The maximum number of deployed API proxies and shared flows per organization is 6000.
• The maximum number of proxy deployment units per Apigee instance is 6000.
• The maximum number of API base paths per Apigee organization is 3000.

When 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.

Note: Enhanced proxy limits feature is only available for new hybrid organizations. This feature is available exclusively as part of the2024 subscription plan, and is subject to the entitlements granted under that subscription. They cannot be enabled on existing organizations.

Provisioning

To provision a new org with the enhanced number of proxies per environment:

1. Provide your project ID and organization name to your Apigee representative to set up the enhanced proxy limit.
2. Follow the Apigee hybridinstallation instructions to provision the hybrid org. In your overrides file, add theenhanceProxyLimits top-level property:

   enhanceProxyLimits: true

   Apply changes toenhanceProxyLimits by updating theapigee-org chart and theapigee-virtualhost chart for every environment group.

   Alert: Do not change this value once set.
3. Create and deploy a proxy.
4. Verify that the enhanced proxy limits are enabled:
   1. Get the name of the configmap for your Apigee namespace:

      kubectl get configmap -nAPIGEE_NAMESPACE

      Your output should look similar to the following:

      NAME                                                             DATA   AGE...apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a       3      12m...

   2. Check the named configmap:

      kubectl get configmap -nAPIGEE_NAMESPACECONFIGMAP_NAME -o yaml

      WhereCONFIGMAP_NAME is the name of the configmap from the previous step.

      Your output should look similar to the following:

      kubectl get configmap -n apigee apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a -o yamlapiVersion: v1data:contract.revid: "2"contract.uid: 4a792429-20fb-4b29-bed3-3f8ce7b3353edeploymentGroups: auto-2ecde5ae-04kind: ConfigMapmetadata:creationTimestamp: "2024-05-15T20:04:26Z"labels:    apigee.cloud.google.com/platform: apigeename: apigee-synchronizer-hybr-test-env-dggroupconfi-bc7726anamespace: apigeeownerReferences:- apiVersion: apigee.cloud.google.com/v1alpha2    blockOwnerDeletion: true    controller: true    kind: ApigeeEnvironment    name: hybrid-dev--test-env-4f37f70    uid: 696e84ec-5c54-4858-a2e0-e36db5ff3506resourceVersion: "2520100"uid: b297bd33-300a-48cf-bf85-6c7cd0ff288f

5. Check for the existence of runtime pods containing the substringauto:

   kubectl get pods -nAPIGEE_NAMESPACE | grep auto

   Your output should look similar to the following:

   kubectl get pods -n apigee | grep autoapigee-runtime-hybr-test-env-auto-2ecde5a-bca5298-4gsrw   1/1     Running     0                98m

Limitations

Apigee offers enhanced per-environment proxy limits only on newly created orgs. Converting existing orgs to use enhanced proxy limits is not supported.

Backups of an organization that was created without enhanced proxy limits enabled cannot be restored to an organization created with the feature enabled.

Known issues

• Proxy chaining:
  • Proxy chaining with mTLS is not supported. Seeknown issue 392135466.