1.0.0 (GA) - Apigee hybrid runtime release notes

You're viewing Apigee Edge documentation.
View Apigee X documentation.

On November 20, 2019, Google released Apigee hybrid runtime version 1.0.0. This section describes bug fixes and known issues with version 1.0.0.

Known issues (GA)

The following table describes the known issues for this release:

Issue Description
144886537 Base path routing is not working in Apigee hybrid v1.0.0. When the overrides is setup to route to different environments with the same hostAlias, the ingress does not route to the environment based on path.
144584813 If you create a debug session but the session does not yet have any transactions in it, then the List Debug Sessions API does not include the session in this list. The API only includes sessions in the response if the session contains at least one transaction.
144436206 In the Cache Performance view, the Cache Hit Ratio calculation is incorrect.
144321491 Apigee hybrid logs "Creating missing cache" notifications that indicate a potential performance degradation. These messages are expected and can be ignored.
144321144 Proxies with secure virtual hosts cannot be reloaded.

Debug mask in env.json does not mask response data.

The following API to update the env.json debug mask with a responseJSONPaths field does not work:

PATCH /v1/organizations/org/environments/env/debugmask?replaceRepeatedFields=true
  "responseJSONPaths": ["$.maskedDataEnv"]

To work around this issue with trace, you can delete an entire trace session in the UI, or you can use the trace APIs to delete individual transactions within a session.

143774187 The hybrid UI displays the label "Company" in the Apps view.

The PopulateCache policy's expiration setting must be set to an explicit value between 1 and 30. For example:


Summary: There is a very high latency when using the API or UI to get your organization's deployment status. This latency can result in an HTTP 204 (No Content) or an HTTP 400 (Bad Request) response.

Workaround: Refresh your browser (or resend the request).

123932912 With zero-downtime deployment, when deployment of a new revision fails, the original revision is still undeployed. You will have to re-deploy the original revision in order to restore its deployment status.

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.

Bugs fixed

The following issues listed in the Apigee hybrid Beta 2 release notes have been fixed:

Issue Description

The update developer apps API does not support all documented input fields.


There is a very high latency when using the API or UI to get your organization's deployment status. This latency can result in an HTTP 204 (No Content) or an HTTP 400 (Bad Request) response.


Synchronizer fails when file system gets too full. This is due to the Kubernetes garbage collection process: it is not triggered until it reaches 85% by default.

Closed: Not reproducible.

Unsupported Apigee Edge features

Google does not plan to support the following features in Apigee hybrid:

  • APIs to:
    • Manipulate KVM entries
    • Search for or revoke OAuth access tokens (because tokens are hashed)
  • Developer portal development using Drupal 7
  • OAuth v1 or OAuthv1.0a policy
  • ConcurrentRateLimit policy rate limiting policy
  • Trireme (EOL'd on 10/10/2019)

For a full comparision of features between hybrid and Edge, see Compare hybrid to Edge.

Next step