viewing Apigee X documentation.
View Apigee Edge documentation.
On March 1, 2021, we released Apigee hybrid runtime version 1.4.2.
Help & notifications
The steps to upgrade to Apigee hybrid version 1.4.2 depend on the version you are upgrading from as shown in the following table:
|Current hybrid version||Upgrade to hybrid version||Instructions|
|1.3.x||1.4||Upgrading Apigee hybrid to version 1.4.2|
|1.2.x||1.3||Upgrading Apigee hybrid to version 1.3.x|
|1.x||1.2||Upgrading to version 1.2.x|
For changes introduced in Apigee hybrid version 1.4.1, see the 1.4.1 - Apigee hybrid runtime release notes.
Apigee hybrid version 1.4.2 includes a security update for a vulnerability in fluentd.
The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|180128329||In Apigee hybrid version 1.4.2, Kubernetes service ports were renamed to follow Istio standards.|
|179891322||Backup and recovery of the Cssandra database without Google Cloud was not working in some instances. See Backup and recovery without Google Cloud.|
|179461749||Non-default Cassandra passwords can now be configured using Kubernetes secrets.|
|178829167||When synchronizer would go down the error messages indicated apigee-runtime was down.|
|178732212||Documentation for Cassandra backup and recovery has been updated. See Cassandra backup and recovery.|
|177681383||Watcher has added timeouts to handle connection timeouts to Apigee management plane in order to properly handle the stale connections. This eliminates some conditions where apigee-watcher could become stuck.|
The following table describes the known issues for this release:
|175878028||On upgrading to hybrid version 1.4.2, all runtime components will undergo a rolling restart.|
|146222881||Invalid HTTP Header error: The Istio ingress switches all incoming target responses to the
HTTP2 protocol. Because the hybrid message processor only supports HTTP1, you may see the
following error when an API proxy is called:
If you see this error, you can take either of the following actions to correct the problem: