<?xml version="1.0" encoding="UTF-8"?>
<!-- AUTOGENERATED FILE. DO NOT EDIT. -->
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>tag:google.com,2016:apigee-envoy-adapter-release-notes</id>
  <title>Apigee Adapter for Envoy - Release notes</title>
  <link rel="self" href="https://docs.cloud.google.com/feeds/apigee-envoy-adapter-release-notes.xml"/>
  <author>
    <name>Google Cloud Platform</name>
  </author>
  <updated>2023-07-07T00:00:00-07:00</updated>

  <entry>
    <title>July 07, 2023</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#July_07_2023</id>
    <updated>2023-07-07T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#July_07_2023"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title"></strong>
<h3>Announcement</h3>
<h3 id="v211">v2.1.1</h3>
<p>On June 7, 2023, we released version 2.1.1 of Apigee Adapter for Envoy.</p>
<h3>Fixed</h3>
<p>An issue was fixed where quotas were being improperly duplicated between operations instead of being shared at the Product level.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>June 05, 2023</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#June_05_2023</id>
    <updated>2023-06-05T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#June_05_2023"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title">v2.1.0</strong>
<h3>Announcement</h3>
<h3 id="v210">v2.1.0</h3>
<p>On June 5, 2023, we released version 2.1.0 of Apigee Adapter for Envoy.</p>
<h3>Fixed</h3>
<p>The <code>application_id</code> claim was added to the <code>/verifyApiKey</code> response.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 09, 2023</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#March_09_2023</id>
    <updated>2023-03-09T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#March_09_2023"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title">v2.0.7</strong>
<h3>Announcement</h3>
<h3 id="v207">v2.0.7</h3>
<p>On March 9, 2023, we released version 2.0.7 of Apigee Adapter for Envoy.</p>
<p><strong>Note:</strong> If you are <strong>upgrading</strong> an existing Apigee Adapter for Envoy, you <strong>must</strong> add the <code>--force-proxy-install</code> flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See <a href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/latest/example-hybrid">Apigee hybrid example</a>.</p>
<h3>Fixed</h3>
<ul>
<li>An issue was fixed where an invalid api key could create spurious log entries and analytics records.</li>
<li>A deprecated version check was removed in a proxy that caused issues in newer versions of Apigee.</li>
</ul>
<h3>Feature</h3>
<p>JWTs can now add a claim named <code>customattributes</code> that will pass the value on to the target in a header called <code>x-apigee-customattributes</code> (if <code>append_metadata_headers</code> is configured to be true).</p>
]]>
    </content>
  </entry>

  <entry>
    <title>October 18, 2022</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#October_18_2022</id>
    <updated>2022-10-18T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#October_18_2022"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title">v2.0.6</strong>
<h3>Announcement</h3>
<h3 id="v206">v2.0.6</h3>
<p>On October 18, 2022, we released version 2.0.6 of Apigee Adapter for Envoy.</p>
<h3>Change</h3>
<p>Security release to address a Denial of Service (DoS) vulnerability in a dependency library. See <a href="https://www.cve.org/CVERecord?id=CVE-2022-28948">CVE-2022-28948</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>March 03, 2022</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#March_03_2022</id>
    <updated>2022-03-03T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#March_03_2022"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title">v2.0.5</strong>
<h3>Announcement</h3>
<h3 id="envoy_adapter_v205">Envoy adapter v2.0.5</h3>
<p>On March 3, 2022 we released a new version of Apigee Adapter for Envoy v2.0.5.</p>
<h3>Security</h3>
<p>Security release to address a Denial of Service (DoS) risk in the prometheus library. See <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21698">CVE-2022-21698</a>.</p>
]]>
    </content>
  </entry>

  <entry>
    <title>December 03, 2021</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#December_03_2021</id>
    <updated>2021-12-03T00:00:00-08:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#December_03_2021"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title">v2.0.4</strong>
<h3>Announcement</h3>
<h3 id="v204">v2.0.4</h3>
<p>On December 3, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.4 software.</p>
<aside class="note"><strong>Note:</strong><span> If you are upgrading an existing Apigee Adapter for Envoy, you must add the <code>--force-proxy-install</code> flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See <a href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/latest/example-hybrid">Apigee hybrid example</a>.</span></aside>
<p><details>
<summary>▶ Click to see the list of supported platforms.</summary></details></p>
<p>We publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:</p>
<ul>
<li>Apigee hybrid version 1.4.x, 1.5.x, 1.6.x</li>
<li>Apigee X</li>
<li>Apigee Edge for Public Cloud</li>
<li>Apigee Edge for Private Cloud</li>
<li>Istio versions 1.10, 1.11, 1.12</li>
<li><p>Envoy versions 1.17, 1.18, 1.19, 1.20</p>
<p></p></li>
</ul>
<h3>Feature</h3>
<p><strong>The list of supported Envoy and Istio versions for the CLI samples command has been updated.</strong> These versions are now supported for samples:</p>
<ul>
<li>Envoy versions 1.18 to 1.20</li>
<li>Istio versions 1.10 to 1.12</li>
</ul>
<h3>Fixed</h3>
<table>
<thead>
<tr>
<th>Bug ID</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>360</strong></td>
<td>A nil-check was added for the PEM block private key loading to avoid panic.</td>
</tr>
<tr>
<td><strong>104</strong></td>
<td>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 <a href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/v2.0.x/troubleshooting#settingremoteserviceloglevels">Setting remote service log levels</a>.</td>
</tr>
</tbody>
</table>
]]>
    </content>
  </entry>

  <entry>
    <title>September 21, 2021</title>
    <id>tag:google.com,2016:apigee-envoy-adapter-release-notes#September_21_2021</id>
    <updated>2021-09-21T00:00:00-07:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/release-notes#September_21_2021"/>
    <content type="html"><![CDATA[<strong class="release-note-product-version-title">v2.0.3</strong>
<h3>Fixed</h3>
<table>
<thead>
<tr>
<th>Bug ID</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>N/A</strong></td>
<td><strong>An analytics logging issue with direct responses was fixed.</strong> 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.</td>
</tr>
</tbody>
</table>
<h3>Announcement</h3>
<h3 id="v203">v2.0.3</h3>
<p>On September 21, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.3 software.</p>
<aside class="note"><strong>Note:</strong><span> If you are upgrading an existing Apigee Adapter for Envoy, you must add the <code>--force-proxy-install</code> flag to the provision command. This flag forces the Apigee proxy to be replaced with the latest proxy. See <a href="https://docs.cloud.google.com/apigee/docs/api-platform/envoy-adapter/latest/example-hybrid">Apigee hybrid example</a>.</span></aside>
<p><details>
<summary>▶ Click to see the list of supported platforms.</summary></details></p>
<p>We publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:</p>
<ul>
<li>Apigee hybrid version 1.4.x, 1.5.x, 1.6.x</li>
<li>Apigee X</li>
<li>Apigee Edge for Public Cloud</li>
<li>Apigee Edge for Private Cloud</li>
<li>Istio versions 1.10, 1.11, 1.12</li>
<li><p>Envoy versions 1.17, 1.18, 1.19</p>
<p></p></li>
</ul>
]]>
    </content>
  </entry>

</feed>
