On September 20, 2020, we released Apigee hybrid runtime version 1.3.3.
Help & notifications
Apigee hybrid version 1.3.x to version 1.3.3
To upgrade from hybrid version 1.3.x to version 1.3.3:
- Delete the apigee resources in the
kubectl -n apigee-system delete job apigee-resources-install
- Download the new hybrid runtime.
Platform Download hybrid runtime Mac 64 bit
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.3/apigeectl_mac_64.tar.gz
Linux 64 bit
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.3/apigeectl_linux_64.tar.gz
Mac 32 bit
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.3/apigeectl_mac_32.tar.gz
Linux 32 bit
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.3/apigeectl_linux_32.tar.gz
Apigee hybrid version 1.2.0 to version 1.3.3
To upgrade from hybrid version 1.2.0 to version 1.3.3 follow the instructions in Upgrading Apigee hybrid to version 1.3.3.
Apigee hybrid version 1.1.1 or older to version 1.3.3
If you are upgrading from Apigee hybrid version 1.0 or 1.1, you must first upgrade to hybrid version 1.2 before upgrading to version 1.3.3. See the instructions for Upgrading Apigee hybrid to version 1.2.
Changes introduced in this release
The Target latency metric was removed from from the
For changes introduced in Apigee hybrid version 1.3.2, see the 1.3.2 - Apigee hybrid runtime release notes
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.
|167650106||Unable to use PUT to insert entries into an encrypted KVM when the environment name
contained a hyphen (
The following table describes the known issues for this release:
Double slashes (
|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: