You're viewing Apigee Edge documentation.
View Apigee X documentation.
On February 14, 2020, we released Apigee hybrid runtime version 1.1.1.
You cannot upgrade from 1.0.0 to 1.1.1, and the new version is not backward compatible with version 1.0.0. If you are starting with version 1.0.0, version 1.1.1 requires a new installation. If you are currently on version 1.1.0, you can upgrade by following these instructions: Upgrading Apigee hybrid.
New features and updates
Following are the new features and enhancements in this release:
Support for GKE on-prem and AKS
You can now install the hybrid runtime on Anthos GKE deployed on-prem (GKE on-prem) and Microsoft® Azure Kubernetes Service (AKS). See Part 2: Runtime quickstart to get started.
Proxy variables for hybrid components
You can now provide configuration parameters for an HTTP forward proxy server. When
configured, all internet communication for the UDCA, MART, and Synchronizer components
pass through the proxy server. For information about the
property, see httpProxy properties.
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||Component Name||Description|
Discrepancy in UDCA metric
Turn partitioned hash index on in hybrid
An issue was fixed where the Debug mask in
Contract encryption key should not be part of
Remove unwanted ports from the istio ingress
Ingress logs are not collected
com.apigee.test.runtime.steps.quota.DefaultQuotaTypeTest fails in hybrid
There are currently two correlation IDs for one transaction. We should have only one.
UDCA: remove no health check warning in logging
CacheConfiguration.warnMaxEntriesLocalHeap() Log statement indicates a performance issue
The following table describes the known issues for this release:
|150187652||You cannot use hyphens in environment names. An environment name with a hyphen causes runtime pod startup errors.|
When upgrading to version 1.1.1, previously deployed proxies will not be deployed.
Workaround: To work around this issue, redeploy any previously deployed proxies.
|N/A||You cannot use a "*" for the |
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:
|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.|
|144321144||Proxies with secure virtual hosts cannot be reloaded.|
The PopulateCache policy's expiration setting must be set to an explicit value between 1 and 30. For example:
<ExpirySettings> <TimeoutInSec>30</TimeoutInSec> </ExpirySettings>
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
Workaround: Refresh your browser (or resend the request).