diff --git a/CHANGELOG.md b/CHANGELOG.md index b8f925e34e..1f4759da69 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -85,7 +85,7 @@ it will be removed; but as it won't be user-visible this isn't considered a brea ## RELEASE NOTES -## [3.4.0] TBD +## [3.4.0] January 03, 2023 [3.4.0]: https://github.com/emissary-ingress/emissary/compare/v3.3.0...v3.4.0 ### Emissary-ingress and Ambassador Edge Stack @@ -97,18 +97,6 @@ it will be removed; but as it won't be user-visible this isn't considered a brea Kubernetes Nodes (regardless of whether the installation was migrated from 1.y or was a fresh 2.y install); fully supporting `v1` again should resolve these errors. -- Security: Update Golang to release 1.19.4. Two CVE's were annouced in this z patch release. - CVE-2022-41720 only affects Windows environments and Emissary-ingress runs in linux. The second - one CVE-2022-41717 only affects HTTP/2 server connections exposed to external clients. - Emissary-ingress does not expose any Golang http servers to outside clients. The data-plane of - Envoy is not affected by either of these. - -- Security: Updated Golang to the latest z patch. We are not vulnerable to the CVE-2022-3602 that - was released in 1.19.3 and you can read more about it here: - . - Updating to the latest z patch as part of our normal dependency update process and this will help - reduce the noise of security scanners. - - Feature: It is now possible to configure active healhchecking for upstreams within a `Mapping`. If the upstream fails its configured health check then Envoy will mark the upstream as unhealthy and no longer send traffic to that upstream. Single pods within a group may can be marked as diff --git a/charts/emissary-ingress/CHANGELOG.md b/charts/emissary-ingress/CHANGELOG.md index ec749b2662..203d8c2cd7 100644 --- a/charts/emissary-ingress/CHANGELOG.md +++ b/charts/emissary-ingress/CHANGELOG.md @@ -3,10 +3,12 @@ This file documents all notable changes to Ambassador Helm Chart. The release numbering uses [semantic versioning](http://semver.org). -## v8.4.0 - TBD +## v8.4.0 - 2022-01-03 - Upgrade Emissary to v3.4.0 [CHANGELOG](https://github.com/emissary-ingress/emissary/blob/master/CHANGELOG.md) +- The Ambassador agent that was previously embedded in Emissary Ingress has been moved to a standalone container. + ## v8.3.0 - Upgrade Emissary to v3.3.0 [CHANGELOG](https://github.com/emissary-ingress/emissary/blob/master/CHANGELOG.md) diff --git a/docs/releaseNotes.yml b/docs/releaseNotes.yml index d667ce1a8a..54636de0a8 100644 --- a/docs/releaseNotes.yml +++ b/docs/releaseNotes.yml @@ -34,7 +34,7 @@ changelog: https://github.com/emissary-ingress/emissary/blob/$branch$/CHANGELOG. items: - version: 3.4.0 prevVersion: 3.3.0 - date: 'TBD' + date: '2023-01-03' notes: - title: Re-add support for getambassador.io/v1 type: feature @@ -47,23 +47,6 @@ items: installation was migrated from 1.y or was a fresh 2.y install); fully supporting v1 again should resolve these errors. - - title: Update Golang to 1.19.4 - type: security - body: >- - Update Golang to release 1.19.4. Two CVE's were annouced in this z patch release. - CVE-2022-41720 only affects Windows environments and $productName$ runs in linux. The second one - CVE-2022-41717 only affects HTTP/2 server connections exposed to external clients. $productName$ does - not expose any Golang http servers to outside clients. The data-plane of Envoy - is not affected by either of these. - - - title: Update Golang to 1.19.3 - type: security - body: >- - Updated Golang to the latest z patch. We are not vulnerable to the CVE-2022-3602 that was - released in 1.19.3 and you can read more about it here: . - Updating to the latest z patch as part of our normal dependency update process - and this will help reduce the noise of security scanners. - - title: Add support for active health checking configuration. type: feature body: >- @@ -71,7 +54,7 @@ items: If the upstream fails its configured health check then Envoy will mark the upstream as unhealthy and no longer send traffic to that upstream. Single pods within a group may can be marked as unhealthy. The healthy pods will continue to receive traffic normally while the unhealthy pods will not receive any traffic until they recover by passing the health check. - + - title: Add environment variables to the healthcheck server. type: feature body: >-