> [!CAUTION]
> You are currently viewing version 1.1 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.1 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/revision.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/revision.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/revision.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/revision.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/revision.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/revision.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/revision.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/revision.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/revision.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/revision.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/revision.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/revision.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/revision.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/revision.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/revision.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/revision.md.txt)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/revision.md.txt)


Apigee hybrid supports [rolling
updates](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/). In Kubernetes, rolling updates allow Deployment updates to take place with zero
downtime by incrementally updating Pod instances with new ones.

## Components that support rolling updates


If you change property settings for any hybrid of the following components in your
overrides file, you can use
the `revision` property to signal that you want to perform a rolling update
to the affected pods.

- `runtime`
- `mart`
- `udca`
- `metrics`
- `synchronizer`

You can also use `revision` when you change any
of the following properties:

- `nodeSelector.*`
- `envs.*`
- `imagePullSecrets.*`
- `gcpProjectID`
- `k8sClusterName`
- `contractProvider`
- `org`

## How to perform a rolling update


For example, suppose you want to change the current `runtime` memory from 1Gi to
5Gi:


In the current configuration, `revision` is set to `blue`:

```
...
revision: blue
...
runtime:
  replicaCountMin: 2
  replicaCountMax: 20
  resources:
    cpu: 1000m
    memory: 1Gi
...
```


In the new configuration, `revision` is changed to `green`, signaling
that you want to perform a rolling update when
the change is applied. The value you set `revision` to does not matter; you can
use any string you wish, as long as you change it from the previous value to something else.

```
...
revision: green
...
runtime:
  replicaCountMin: 2
  replicaCountMax: 20
  resources:
    cpu: 1000m
    memory: 5Gi
...
```


When you apply the change, you can use the `-c` flag to only update a specific
pod. For example:

```
apigeectl apply -f my-overrides.yaml -c runtime
```


Or, if you do not use `-c` all of the pods that have config changes will be updated.