Stay organized with collections
Save and categorize content based on your preferences.
This page documents production updates to Apigee Adapter for Envoy in 2022
and later. We recommend that users periodically check this list for any new
announcements, or subscribe to this page using a
feed reader to get notifications of updates.
What is a feed reader?
Really simple syndication (RSS) feed readers aggregate content from
websites that you specify.
Feed reader notifications can be email-, browser-, desktop-, or
mobile-based. Some readers are free, or have free versions, and some
require a subscription.
You can see the latest product updates for all of Google Cloud on the
Google Cloud page, browse and filter all release notes in the
Google Cloud console,
or programmatically access release notes in
BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your
feed
reader, or add the
feed URL directly.
July 07, 2023
v2.1.1
v2.1.1
On June 7, 2023, we released version 2.1.1 of Apigee Adapter for Envoy.
An issue was fixed where quotas were being improperly duplicated between operations instead of being shared at the Product level.
June 05, 2023
v2.1.0
v2.1.0
On June 5, 2023, we released version 2.1.0 of Apigee Adapter for Envoy.
The application_id claim was added to the /verifyApiKey response.
March 09, 2023
v2.0.7
v2.0.7
On March 9, 2023, we released version 2.0.7 of Apigee Adapter for Envoy.
Note: If you are upgrading an existing Apigee Adapter for Envoy, you must add the --force-proxy-install flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See Apigee hybrid example.
JWTs can now add a claim named customattributes that will pass the value on to the target in a header called x-apigee-customattributes (if append_metadata_headers is configured to be true).
An issue was fixed where an invalid api key could create spurious log entries and analytics records.
A deprecated version check was removed in a proxy that caused issues in newer versions of Apigee.
October 18, 2022
v2.0.6
v2.0.6
On October 18, 2022, we released version 2.0.6 of Apigee Adapter for Envoy.
Security release to address a Denial of Service (DoS) vulnerability in a dependency library. See CVE-2022-28948.
March 03, 2022
v2.0.5
Envoy adapter v2.0.5
On March 3, 2022 we released a new version of Apigee Adapter for Envoy v2.0.5.
Security release to address a Denial of Service (DoS) risk in the prometheus library. See CVE-2022-21698.
December 03, 2021
v2.0.4
v2.0.4
On December 3, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.4 software.
▶ Click to see the list of supported platforms.
We publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:
Apigee hybrid version 1.4.x, 1.5.x, 1.6.x
Apigee X
Apigee Edge for Public Cloud
Apigee Edge for Private Cloud
Istio versions 1.10, 1.11, 1.12
Envoy versions 1.17, 1.18, 1.19, 1.20
Bug ID
Description
360
A nil-check was added for the PEM block private key loading to avoid panic.
104
Remote service authorization errors are now logged at the Debug level. An exception to this categorization is made for token fetching errors for API keys. In that case, errors are logged at the Error level so that they are visible even if Debug log level for apigee-remote-service-envoy is disabled. See also Setting remote service log levels.
The list of supported Envoy and Istio versions for the CLI samples command has been updated. These versions are now supported for samples:
Envoy versions 1.18 to 1.20
Istio versions 1.10 to 1.12
September 21, 2021
v2.0.3
v2.0.3
On September 21, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.3 software.
▶ Click to see the list of supported platforms.
We publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:
Apigee hybrid version 1.4.x, 1.5.x, 1.6.x
Apigee X
Apigee Edge for Public Cloud
Apigee Edge for Private Cloud
Istio versions 1.10, 1.11, 1.12
Envoy versions 1.17, 1.18, 1.19
Bug ID
Description
N/A
An analytics logging issue with direct responses was fixed. The issue only occurred under certain circumstances. For example: a) For requests not requiring authn/z check, no authContext was generated and dynamic metadata was nil causing the access log entry to be ignored. b) The denied response used RPC code instead of HTTP code, causing records to be shown in the Apigee UI as success.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis page provides a log of production updates for Apigee Adapter for Envoy from 2022 onward, and users are encouraged to check it regularly for new announcements.\u003c/p\u003e\n"],["\u003cp\u003eUsers can subscribe to this page for automatic updates using a feed reader, which aggregates content from specified websites and provides notifications.\u003c/p\u003e\n"],["\u003cp\u003eRecent releases of the Apigee Adapter for Envoy include version 2.1.1 with a fix for quota duplication, version 2.1.0 with an added \u003ccode\u003eapplication_id\u003c/code\u003e claim, and version 2.0.7 which includes JWT custom attributes and bug fixes.\u003c/p\u003e\n"],["\u003cp\u003eSecurity releases were implemented in versions 2.0.6 and 2.0.5 to resolve Denial of Service vulnerabilities in dependency libraries.\u003c/p\u003e\n"],["\u003cp\u003eUpgrading to the latest versions of Apigee Adapter for Envoy requires the \u003ccode\u003e--force-proxy-install\u003c/code\u003e flag in the provision command to ensure the latest proxy is in use.\u003c/p\u003e\n"]]],[],null,["# Apigee Adapter for Envoy release notes\n\nThis page documents production updates to Apigee Adapter for Envoy in 2022\nand later. We recommend that users periodically check this list for any new\nannouncements, or [subscribe](#sub) to this page using a\nfeed reader to get notifications of updates.\nWhat is a feed reader? \n\n### What is a feed reader?\n\nReally simple syndication (RSS) feed readers aggregate content from\nwebsites that you specify.\n\nFeed reader notifications can be email-, browser-, desktop-, or\nmobile-based. Some readers are free, or have free versions, and some\nrequire a subscription.\n\nA few examples:\n\n- [Feedly](https://feedly.com)\n- [Feedreader](https://feedreader.com)\n- [Feeder](https://feeder.co/)\n\nMore information on RSS:\n\n- [RSS](https://en.wikipedia.org/wiki/RSS)\n- [Comparison of feed aggregators](https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators) \nClose\n\n\u003cbr /\u003e\n\nSee also:\n\n- [2021 and prior Release notes](/apigee/docs/release/notes/100-envoy-adapter-release-notes)\n- [Known issues](/apigee/docs/release/known-issues)\n\n\nrss_feed Subscribe:\n\nYou can see the latest product updates for all of Google Cloud on the\n[Google Cloud](/release-notes) page, browse and filter all release notes in the\n[Google Cloud console](https://console.cloud.google.com/release-notes),\nor programmatically access release notes in\n[BigQuery](https://console.cloud.google.com/bigquery?p=bigquery-public-data&d=google_cloud_release_notes&t=release_notes&page=table).\n\nTo get the latest product updates delivered to you, add the URL of this page to your\n[feed\nreader](https://wikipedia.org/wiki/Comparison_of_feed_aggregators), or add the\n[feed URL](https://cloud.google.com/feeds/apigee-envoy-adapter-release-notes.xml) directly.\n\nJuly 07, 2023\n-------------\n\nv2.1.1 \n\n### v2.1.1\n\nOn June 7, 2023, we released version 2.1.1 of Apigee Adapter for Envoy. \nAn issue was fixed where quotas were being improperly duplicated between operations instead of being shared at the Product level.\n\nJune 05, 2023\n-------------\n\nv2.1.0 \n\n### v2.1.0\n\nOn June 5, 2023, we released version 2.1.0 of Apigee Adapter for Envoy. \nThe `application_id` claim was added to the `/verifyApiKey` response.\n\nMarch 09, 2023\n--------------\n\nv2.0.7 \n\n### v2.0.7\n\nOn March 9, 2023, we released version 2.0.7 of Apigee Adapter for Envoy.\n\n**Note:** If you are **upgrading** an existing Apigee Adapter for Envoy, you **must** add the `--force-proxy-install` flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See [Apigee hybrid example](https://cloud.google.com/apigee/docs/api-platform/envoy-adapter/latest/example-hybrid). \nJWTs can now add a claim named `customattributes` that will pass the value on to the target in a header called `x-apigee-customattributes` (if `append_metadata_headers` is configured to be true). \n- An issue was fixed where an invalid api key could create spurious log entries and analytics records.\n- A deprecated version check was removed in a proxy that caused issues in newer versions of Apigee.\n\nOctober 18, 2022\n----------------\n\nv2.0.6 \n\n### v2.0.6\n\nOn October 18, 2022, we released version 2.0.6 of Apigee Adapter for Envoy. \nSecurity release to address a Denial of Service (DoS) vulnerability in a dependency library. See [CVE-2022-28948](https://www.cve.org/CVERecord?id=CVE-2022-28948).\n\nMarch 03, 2022\n--------------\n\nv2.0.5 \n\n### Envoy adapter v2.0.5\n\nOn March 3, 2022 we released a new version of Apigee Adapter for Envoy v2.0.5. \nSecurity release to address a Denial of Service (DoS) risk in the prometheus library. See [CVE-2022-21698](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21698).\n\nDecember 03, 2021\n-----------------\n\nv2.0.4 \n\n### v2.0.4\n\nOn December 3, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.4 software.\n| **Note:** If you are upgrading an existing Apigee Adapter for Envoy, you must add the `--force-proxy-install` flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See [Apigee hybrid example](https://cloud.google.com/apigee/docs/api-platform/envoy-adapter/latest/example-hybrid).\n\n\u003cbr /\u003e\n\n▶ Click to see the list of supported platforms.\n\n\u003cbr /\u003e\n\nWe publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:\n\n- Apigee hybrid version 1.4.x, 1.5.x, 1.6.x\n- Apigee X\n- Apigee Edge for Public Cloud\n- Apigee Edge for Private Cloud\n- Istio versions 1.10, 1.11, 1.12\n- Envoy versions 1.17, 1.18, 1.19, 1.20\n\n \u003cbr /\u003e\n\n\u003cbr /\u003e\n\n**The list of supported Envoy and Istio versions for the CLI samples command has been updated.** These versions are now supported for samples:\n\n- Envoy versions 1.18 to 1.20\n- Istio versions 1.10 to 1.12\n\nSeptember 21, 2021\n------------------\n\nv2.0.3 \n\n### v2.0.3\n\nOn September 21, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.3 software.\n| **Note:** If you are upgrading an existing Apigee Adapter for Envoy, you must add the `--force-proxy-install` flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See [Apigee hybrid example](https://cloud.google.com/apigee/docs/api-platform/envoy-adapter/latest/example-hybrid).\n\n\u003cbr /\u003e\n\n▶ Click to see the list of supported platforms.\n\n\u003cbr /\u003e\n\nWe publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:\n\n- Apigee hybrid version 1.4.x, 1.5.x, 1.6.x\n- Apigee X\n- Apigee Edge for Public Cloud\n- Apigee Edge for Private Cloud\n- Istio versions 1.10, 1.11, 1.12\n- Envoy versions 1.17, 1.18, 1.19\n\n \u003cbr /\u003e\n\n\u003cbr /\u003e"]]
