[v2.3.0] Release PR

Signed-off-by: Lance Austin <[email protected]>

CHANGELOG.md

@@ -66,7 +66,7 @@ refer both to Emissary-ingress and to the Ambassador Edge Stack.
    value.
 
    Users who rely on `HTTP_JSON_V1` will need to migrate their Emissary-ingress 2.3 install to use
-   to either `HTTP_JSON` or `HTTP_PROTO` before upgrading to Emissary-ingress 3.0.0.
+   either `HTTP_JSON` or `HTTP_PROTO` before upgrading to Emissary-ingress 3.0.0.
 
 With the removal of `regex_type: unsafe` and `collector_endpoint_version: HTTP_JSON_V1`, there will
 be no more user-visible effects of the `AMBASSADOR_ENVOY_API_VERSION` environment variable, and so
@@ -82,7 +82,7 @@ it will be removed; but as it won't be user-visible this isn't considered a brea
 
 ## RELEASE NOTES
 
-## [2.3.0] TBD
+## [2.3.0] June 06, 2022
 [2.3.0]: https://github.com/emissary-ingress/emissary/compare/v2.2.2...v2.3.0
 
 ### Emissary-ingress and Ambassador Edge Stack
@@ -96,7 +96,7 @@ it will be removed; but as it won't be user-visible this isn't considered a brea
   certificates against a certificate revocation list. ([#1743])
 
 - Feature: Previously, a `LogService` would always have Emissary-ingress communicate with the
-  external log servie using the `envoy.service.accesslog.v2.AccessLogService` API.  It is now
+  external log service using the `envoy.service.accesslog.v2.AccessLogService` API. It is now
   possible for the `LogService` to specify `protocol_version: v3` to use the newer
   `envoy.service.accesslog.v3.AccessLogService` API instead.  This functionality is not available if
   you set the `AMBASSADOR_ENVOY_API_VERSION=V2` environment variable.
@@ -114,7 +114,7 @@ it will be removed; but as it won't be user-visible this isn't considered a brea
   HTTP_JSON_V1` when using xDS v3 to configure Envoy (which has been the default since
   Emissary-ingress 1.14.0).  The `HTTP_JSON_V1` value configures Envoy to speak to Zipkin using
   Zipkin's old API-v1, while the `HTTP_JSON` value configures Envoy to speak to Zipkin using
-  Zipkin's new API-v2.  In previous versions of Emissary-ingress it was only possible to use
+  Zipkin's new API-v2. In previous versions of Emissary-ingress it was only possible to use
   `HTTP_JSON_V1` when explicitly setting the `AMBASSADOR_ENVOY_API_VERSION=V2` environment variable
   to force use of xDS v2 to configure Envoy.
 

charts/emissary-ingress/CHANGELOG.md

@@ -3,13 +3,13 @@
 This file documents all notable changes to Ambassador Helm Chart. The release
 numbering uses [semantic versioning](http://semver.org).
 
-## Next Release
+## v7.4.0
 
+- Update change Emissary chart image to version v2.3.0 [CHANGELOG](https://github.com/emissary-ingress/emissary/blob/master/CHANGELOG.md)
 - Add "lifecycle" option to main container. This can be used, for example, to add a lifecycle.preStop hook. Thanks to [Eric Totten](https://github.com/etotten) for the contribution!
-- Add `ambassador_id` to listener manifests rendered when using `createDefaultListeners: true` with `AMBASSADOR_ID` set in environment variables.
-
+- Add `ambassador_id` to listener manifests rendered when using `createDefaultListeners: true` with `AMBASSADOR_ID` set in environment variables. Thanks to [Jennifer Reed](https://github.com/ServerNinja) for the contribution!
 - Feature: Added configurable IngressClass resource to be compliant with Kubernetes 1.22+ ingress specification.
-
+  
 ## v7.2.2
 
 - Update Emissary chart image to version v2.1.2: [CHANGELOG](https://github.com/emissary-ingress/emissary/blob/master/CHANGELOG.md)

docs/CHANGELOG.tpl

@@ -66,7 +66,7 @@ refer both to Emissary-ingress and to the Ambassador Edge Stack.
    value.
 
    Users who rely on `HTTP_JSON_V1` will need to migrate their Emissary-ingress 2.3 install to use
-   to either `HTTP_JSON` or `HTTP_PROTO` before upgrading to Emissary-ingress 3.0.0.
+   either `HTTP_JSON` or `HTTP_PROTO` before upgrading to Emissary-ingress 3.0.0.
 
 With the removal of `regex_type: unsafe` and `collector_endpoint_version: HTTP_JSON_V1`, there will
 be no more user-visible effects of the `AMBASSADOR_ENVOY_API_VERSION` environment variable, and so

docs/releaseNotes.yml

@@ -33,7 +33,7 @@
 changelog: https://github.com/emissary-ingress/emissary/blob/$branch$/CHANGELOG.md
 items:
   - version: 2.3.0
-    date: 'TBD'
+    date: '2022-06-06'
     notes:
       - title: Remove unused packages
         type: security
@@ -60,8 +60,8 @@ items:
         type: feature
         body: >-
           Previously, a <code>LogService</code> would always have $productName$ communicate with the
-          external log servie using the <code>envoy.service.accesslog.v2.AccessLogService</code>
-          API.  It is now possible for the <code>LogService</code> to specify
+          external log service using the <code>envoy.service.accesslog.v2.AccessLogService</code>
+          API. It is now possible for the <code>LogService</code> to specify
           <code>protocol_version: v3</code> to use the newer
           <code>envoy.service.accesslog.v3.AccessLogService</code> API instead.  This functionality
           is not available if you set the <code>AMBASSADOR_ENVOY_API_VERSION=V2</code> environment
@@ -87,7 +87,7 @@ items:
           (which has been the default since $productName$ 1.14.0).  The <code>HTTP_JSON_V1</code>
           value configures Envoy to speak to Zipkin using Zipkin's old API-v1, while the
           <code>HTTP_JSON</code> value configures Envoy to speak to Zipkin using Zipkin's new
-          API-v2.  In previous versions of $productName$ it was only possible to use
+          API-v2. In previous versions of $productName$ it was only possible to use
           <code>HTTP_JSON_V1</code> when explicitly setting the
           <code>AMBASSADOR_ENVOY_API_VERSION=V2</code> environment variable to force use of xDS v2
           to configure Envoy.