ad changelog for Mapping cache fix

Signed-off-by: AliceProxy <[email protected]>

CHANGELOG.md

@@ -104,6 +104,11 @@ Please see the [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest
   processing will happen before authentication. This corrects a problem where XHR to authenticated
   endpoints would fail.
 
+- Bugfix: In 2.x releases of Emissary-ingress when there are multiple `Mapping`s that have the same
+  `metadata.name` across multiple namespaces, their old config would not properly be removed from
+  the cache when their config was updated. This resulted in an inability to update configuration for
+  groups of `Mapping`s that share the same name until the Emissary-ingress pods restarted.
+
 [#4179]: https://github.com/emissary-ingress/emissary/pull/4179
 [#1743]: https://github.com/emissary-ingress/emissary/issues/1743
 

docs/releaseNotes.yml

@@ -62,6 +62,13 @@ items:
           When CORS is specified (either in a <code>Mapping</code> or in the <code>Ambassador</code>
           <code>Module</code>), CORS processing will happen before authentication. This corrects a
           problem where XHR to authenticated endpoints would fail.
+      - title: Correctly handle caching Mappings with the same name in different namespaces
+        type: bugfix
+        body: >-
+          In 2.x releases of $productName$ when there are multiple <code>Mapping</code>s that have the same
+          <code>metadata.name</code> across multiple namespaces, their old config would not properly be removed
+          from the cache when their config was updated. This resulted in an inability to update configuration
+          for groups of <code>Mapping</code>s that share the same name until the $productName$ pods restarted.
 
   - version: 2.2.2
     date: '2022-02-25'