[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-18 (世界標準時間)。"],[[["\u003cp\u003eThe Apigee hybrid documentation version 1.4 is end-of-life, and users should upgrade to a newer version for continued support.\u003c/p\u003e\n"],["\u003cp\u003eScaling parameters for Apigee hybrid runtime services can be configured in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eDifferent services like Cassandra, Ingress/LoadBalancer, Logger, MART Apigee Connect Watcher, and Runtime Synchronizer UDCA have their own specific methods and settings for scaling in Kubernetes, including the use of Horizontal Pod Autoscalers and DaemonSets.\u003c/p\u003e\n"],["\u003cp\u003eAdvanced scaling scenarios, such as setting different scaling options for each environment or component, are possible through the use of the \u003ccode\u003ekubernetes patch\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eScaling of MART, watcher and connect agent are all done by editing the replica count using the same properties, that being replicaCountMin and replicaCountMax.\u003c/p\u003e\n"]]],[],null,[]]