1.3.3 - Apigee hybrid runtime release notes

On September 20, 2020, we released Apigee hybrid runtime version 1.3.3.

Upgrading

Apigee hybrid version 1.3.x to version 1.3.3

To upgrade from hybrid version 1.3.x to version 1.3.3:

  1. Delete the apigee resources in the apigee-system namespace.
    kubectl -n apigee-system delete job apigee-resources-install
  2. Download the new hybrid runtime.
    PlatformDownload 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
  3. Run apigeectl init and apigeectl apply.

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 apigee.googleapis.com/Proxy monitored resource.

For changes introduced in Apigee hybrid version 1.3.2, see the 1.3.2 - Apigee hybrid runtime release notes

Bugs fixed

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.

Issue ID Description
167650106 Unable to use PUT to insert entries into an encrypted KVM when the environment name contained a hyphen (-).

Known issues

The following table describes the known issues for this release:

Issue Description
172332786 Double slashes (//) in a request can cause the request not to resolve. You can solve this by applying a configuration to your Istio ingress that filters for double slashes. See Remove double slashes from requests for instructions.
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:

http2 error: Invalid HTTP header field was received: frame type: 1, stream: 1,

name: [:authority], value: [domain_name]

If you see this error, you can take either of the following actions to correct the problem:

  • Modify the target service to omit the Host header in the response.
  • Remove the Host header using the AssignMessage policy in your API proxy if necessary.