You're viewing Apigee Edge documentation.
View Apigee X documentation.
On April 3, 2020, we released Apigee hybrid runtime version 1.2.0.
Help & notifications
Private Cloud customers: Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see About release numbering to understand how you can figure it out by comparing release numbers.
Questions or issues? Get help here.
Release notifications: Go to http://status.apigee.com and click Subscribe to Updates.
New features and updates
Following are the new features and updates in this release.
A new virtual host configuration was added to specify routing rules
virtualhosts configuration feature addresses an issue
where the order in which base paths were routed to multiple environments was
uncertain. For details, see
Configure virtual hosts. (150336519)
Beta release of the OASValidation policy
The OASValidation (OpenAPI Specification Validation) policy (Beta) enables you to validate an incoming request or response message against an OpenAPI 3.0 Specification (JSON or YAML). For more information, see OASValidation policy (Beta). (144949685)
Beta release of WebSocket support
Apigee hybrid supports WebSocket connections. API proxy clients can now request a protocol upgrade from HTTP to WebSockets. For details, see Using WebSockets (Beta).
Accessing policy secret values from Kubernetes secrets
A new feature lets you access values stored in a Kubernetes secret in proxy flow variables. For details, see Storing data in a Kubernetes secret. (133377603)
Apigee Operators (AO) element replaces ADAC and ADAH
Apigee Operators (AO) Creates and updates low level Kubernetes and Istio resources that are required to deploy and maintain the AD. For example, the controller carries out the release of message processors. Also validates the ApigeeDeployment configuration before persisting it in Kubernetes cluster. AO replaces Apigee Deployment Admissionhook (ADAH) and Apigee Deployment Controller (ADC). See ao in the Configuration property reference. (151250559)
Replace and deprecate certain cluster and project configuration properties
Two new configuration properties were added:
These properties replace the following deprecated properties:
gcpProjectID. For details,
see Configuration property reference. (146299599)
Persistent Volume expansion for Cassandra on Kubernetes
A process was added to expand the persistent volume used by apigee-cassandra to accommodate the storage needs, without needing to add more nodes just to increase storage. See Expand Cassandra persistent volumes. (138167919)
Support additional sources for certs, encryption keys and SAs
New configuration properties were added that provide greater flexibility in the way you specify TLS certificates, encryption keys, and service account keys. The new properties are listed below:
For more information, see the Configuration properties reference. (145303466)
Allow customers to obfuscate data before sending it to analytics
A feature was added that allows you to obfuscate certain analytics data before it is sent to the management plane. For details, see Obfuscate user data for analytics. (142578910)
Expand persistent volumes for statefulsets
A feature was added that allows you expand the persistent volume used by apigee-cassandra to accommodate the storage needs, without adding more compute power. For more information, see Expand persistent volumes for statefulsets. (138167919)
Minimum supported versions of GKE, Anthos, and AKS are upgraded
Apigee hybrid now supports GKE 1.14.x, Anthos 1.2, and AKS 1.14.x. (149578101)
Support TLS 1.3 for Northbound connections
Two new configuration properties allow you to set the minimum and maximum TLS version for
Possible values are 1.0, 1.1, 1.2 and 1.3. For more information, see
properties reference. (117580780)
Support forward proxy configuration for hybrid runtime
HTTP forward proxying is now supported for API proxies deployed to an environment. For details, see Configure forward proxying. (148970527)
Support multiple hostAliases per environment
A new configuration property,
envs.hostAliases, has been added. This
property lets you add multiple host aliases to an environment. Use this element instead of
hostAlias, which has been deprecated. For details, see
multiple host aliases to an environment. (150738495)
Allow templates for property sets
A new element <PropertySetRef> was added to the <AssignVariable> element of the <AssignMessage> policy. <PropertySetRef> allows you to create a property set name/key pair dynamically. This feature is only available for API proxies deployed to Apigee hybrid. See AssignVariable. (148612340)
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|
|147958049||Runtime||A timing issue in runtime startup sequencing was addressed that sometimes prevented the synchronizer from starting up properly.|
|149867244||K8S Platform||apigee-cps-setup pod failing in multi-region setup|
|150187652 / 149117839||Runtime||Could not use hyphens in environment names.|
|149220463||MP pod||Previously deployed proxies needed to be re-deployed.|
|144321144||Runtime||Proxies with secure virtual hosts could not be reloaded.|
|147685310||Runtime||Synchronizer initialization failures due to failed GCP token fetch during initialization.|
|151115900||Runtime||Periodic Internal Probe was not happening for HybridMART resulting in false positive results.|
The following table describes the known issues for this release:
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.|
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).