Organisasi hybrid Apigee baru dapat disediakan dengan kemampuan untuk men-deploy lebih dari 50 proxy per lingkungan yang diaktifkan. Fitur ini juga tersedia untuk Apigee X.
Jumlah maksimum proxy API dan alur bersama yang di-deploy per organisasi adalah 6.000.
Jumlah maksimum unit deployment proxy per instance Apigee adalah 6.000.
Jumlah maksimum jalur dasar API per organisasi Apigee adalah 3.000.
Jika lebih dari 50 proxy di-deploy di lingkungan, Apigee akan otomatis mempartisi lingkungan menjadi beberapa set replika yang berbeda, yang masing-masing berisi subset proxy yang di-deploy di lingkungan. Perilaku subset replika ini setara dengan satu lingkungan dalam cara memuat dan menjalankan kumpulan proxy serta resource lingkungan lainnya. Hal ini akan transparan bagi pengguna, dan Anda dapat terus menggunakan lingkungan seperti menggunakan satu lingkungan.
Penyediaan
Untuk menyediakan organisasi baru dengan jumlah proxy yang ditingkatkan per lingkungan:
Berikan project ID dan nama organisasi Anda kepada perwakilan Apigee untuk menyiapkan batas proxy yang ditingkatkan.
Periksa keberadaan pod runtime yang berisi substring auto:
kubectl get pods -n APIGEE_NAMESPACE | grep auto
Output Anda akan terlihat seperti berikut:
kubectl get pods -n apigee | grep auto
apigee-runtime-hybr-test-env-auto-2ecde5a-bca5298-4gsrw 1/1 Running 0 98m
Batasan
Apigee menawarkan peningkatan batas proxy per lingkungan hanya pada organisasi yang baru dibuat. Konversi organisasi yang ada untuk menggunakan batas proxy yang ditingkatkan tidak didukung.
Cadangan organisasi yang dibuat tanpa mengaktifkan batas proxy yang ditingkatkan tidak dapat dipulihkan ke organisasi yang dibuat dengan mengaktifkan fitur tersebut.
[[["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-18 UTC."],[],[],null,["# Enhanced per-environment proxy limits\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.15/install-before-begin) to provision the hybrid org. In your overrides file, add the [`enhanceProxyLimits`](/apigee/docs/hybrid/v1.15/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)."]]
