Apigee hybrid: Configure runtime rollout strategy
Apigee hybrid now allows configuration of the runtime (message processor) ReplicaSet update rollout strategy. This provides control over update deployments, defaulting to 'rolling' which is suitable for most use cases. Engineers managing hybrid deployments can now specify strategies like 'scale-down-first' or 'none' for finer-grained control.
Features (1) ›
- Apigee hybrid Runtime rollout strategy configuration
Runtime rollout strategy configuration In this release, you can configure the rollout strategy used when updating runtime (message processor) ReplicaSets by setting the runtime.release.strategy property (with options rolling , scale-down-first , or none ) or per-environment with envs[].components.runtime.release.strategy in your overrides configuration file. The property defaults to rolling .
https://docs.cloud.google.com/release-notes#July_23_2026
Related releases
- Cloud SDK 578.0.0: Database Migration default change, AlloyDB backup DR GA, BigQuery improvements Google Cloud release notes ·
- GKE: Opt-out of Arm taint, CORS for Gateways Google Cloud release notes ·
- Confidential VM: August 2026 kernel update may impact AMD SEV-SNP instances Google Cloud release notes ·
- Security Command Center ServiceNow Integration Updates Google Cloud release notes ·
- Compute Engine C4D Instances Increase Hyperdisk Throughput Google Cloud release notes ·
- Spanner allows creating tables without explicit primary keys Google Cloud release notes ·