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
- Config Connector 1.154.1 Adds New Alpha Resources and Field Support Google Cloud release notes ·
- Security Command Center: Data Residency & Agent Vulnerability Scanning Preview Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Private Service Connect changes August 2026 Google Cloud release notes ·
- Cloud SQL for SQL Server: Private Service Connect connection behavior changes Google Cloud release notes ·
- Cloud SQL for MySQL: Private Service Connect and QueryData Updates Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Faster CMEK Re-encryption Google Cloud release notes ·