A configured proxy could be bypassed by the connection agent
Google released Apigee hybrid 1.16.13 on October 30 and explicitly warns against deploying 1.16.12. The associated issue concerns the connection agent used to link a customer-managed runtime to Google's management services.
According to Google's issue record, the agent can ignore HTTPS_PROXY and attempt a direct connection. In clusters whose network policy allows outbound traffic only through an HTTP forward proxy, that attempt times out and management operations can fail. The record identifies seven affected patch versions across the 1.14, 1.15, 1.16 and 1.17 branches.
The fix requires choosing a suitable upgrade path
Google marks the problem fixed in 1.16.13 and 1.17.3, and tells users to avoid both 1.16.12 and 1.17.2. Its 1.16.13 release notes say the corrected agent respects proxy settings, including credentials. The patch also includes other fixes, so it should be reviewed as a complete software update.
CGH perspective: first compare the installed version and outbound proxy configuration with the issue record. Then follow the supported upgrade instructions for that installation and verify the management connection through the intended proxy. A direct-Internet exception would change the network control rather than establish that the regression was fixed.
Scope and verification limits
The reviewed notice concerns Apigee hybrid software, not a universal outage affecting every Apigee customer. Google provides a release date but no exact release time, region-by-region rollout schedule or patch-specific commercial terms. Deployment remains an administrator task. CGH has not reproduced the failure or tested the corrected versions.