[[["容易理解","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\u003eThis version of Apigee hybrid documentation is end of life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid supports in-place updates, which apply configuration changes and use Kubernetes rolling updates to ensure zero downtime by incrementally updating Pod instances.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid also supports AB-style updates (also known as canary updates), where a new revision receives a small percentage of traffic initially, gradually increasing until all traffic is directed to it.\u003c/p\u003e\n"],["\u003cp\u003eIn-place updates are triggered by modifying settings in the overrides file, while AB updates are initiated by changing the \u003ccode\u003erevision\u003c/code\u003e tag in the overrides file.\u003c/p\u003e\n"],["\u003cp\u003eAB updates follow a set schedule where traffic is incrementally shifted to the new revision in stages, such as 5% for 60 seconds, 20% for 10 seconds, and finally 100% for 10 seconds, although these values are not configurable.\u003c/p\u003e\n"]]],[],null,["# Rolling updates\n\n| You are currently viewing version 1.6 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\n\nApigee hybrid supports two kinds of updates. The first is an *in-place update* where\nyou apply a configuration change and hybrid begins a Kubernetes [rolling\nupdate](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/). In Kubernetes, rolling updates allow Deployment updates to take place with zero\ndowntime by incrementally updating Pod instances with new ones.\n\n\nApigee hybrid also supports a canary or AB-style update. In an AB update, the new revision\nis deployed; however, at first a small percentage of traffic is directed to it. Over time, this\npercentage increases until all of the traffic goes to the revision.\n\nIn-place updates\n----------------\n\n\nTo trigger an in-place update, simply modify the desired settings in the overrides file and apply\nit to the cluster. For example, suppose you want to change the current `runtime`\nmemory from 1Gi to 5Gi:\n\n\nHere is the initial configuration: \n\n```text\n...\nruntime:\n replicaCountMin: 2\n replicaCountMax: 20\n resources:\n requests:\n cpu: 1000m\n memory: 1Gi\n...\n```\n\n\nIn the new configuration, memory is changed to 5Gi: \n\n```text\n...\nruntime:\n replicaCountMin: 2\n replicaCountMax: 20\n resources:\n requests:\n cpu: 1000m\n memory: 5Gi\n...\n```\n\n\nWhen you apply the change, the updated pods start up and replace the existing pods. Because of\nthe Kubernetes rolling update feature, clients do not experience any downtime.\n\nHow to perform an AB update\n---------------------------\n\n\nTo perform an AB update, use the `revision` tag in your overrides file.\nFor example, suppose you want to change the current `runtime` memory from 1Gi to\n5Gi:\n\n\nIn the current configuration, `revision` is set to `blue`: \n\n```text\n...\nrevision: blue\n...\nruntime:\n replicaCountMin: 2\n replicaCountMax: 20\n resources:\n requests:\n cpu: 1000m\n memory: 1Gi\n...\n```\n\n\nIn the new configuration, if you change `revision` to `green`, you signal\nthat you want to perform a rolling update when\nthe change is applied. The value you set `revision` to does not matter; you can\nuse any string you wish, as long as you change it from the previous value to something else. \n\n```text\n...\nrevision: green\n...\nruntime:\n replicaCountMin: 2\n replicaCountMax: 20\n resources:\n requests:\n cpu: 1000m\n memory: 5Gi\n...\n```\n\n\nWhen you apply the change, a small percentage of traffic to the new revision. Over time,\nmore traffic goes to the new revision until it reaches 100%. At that time, the old revision\nis deleted.\n\n\nTo trigger an AB rollout, either add the `revision` tag if it is not present,\nor change the value of the `revision` tag if it is already present. You are\nnot required to make any other changes to the overrides file to trigger an AB rollout.\n\n\nThe following table the schedule of an AB rollout:\n\n\nIn the current release, the percentages and wait times are not configurable."]]
