[release/v1.3] fix 1.3.0-rc.1 release note (envoyproxy#5175)

* fix 1.3.0-rc.1 release note

Signed-off-by: Guy Daich <[email protected]>

* more fixes

Signed-off-by: Guy Daich <[email protected]>

---------

Signed-off-by: Guy Daich <[email protected]>

Author: guydc

release-notes/v1.3.0-rc.1.yaml

@@ -3,13 +3,10 @@ date: January 23, 2025
 # Changes that are expected to cause an incompatibility with previous versions, such as deletions or modifications to existing APIs.
 breaking changes: |
   The Container `ports` field of the gateway instance has been removed, which will cause the gateway Pod to be rebuilt when upgrading the version.
-  ClientTrafficPolicy previously treated an empty TLS ALPNProtocols list as being undefined and applied Envoy Gateway defaults.
-  An empty TLS ALPNProtocols list is now treated as user-defined disablement of the TLS ALPN extension.
-  Outlier detection (passive health check) is now disabled by default.
-  refer to https://gateway.envoyproxy.io/docs/api/extension_types/#backendtrafficpolicy for working with passive health checks.
+  ClientTrafficPolicy previously treated an empty TLS ALPNProtocols list as being undefined and applied Envoy Gateway defaults. An empty TLS ALPNProtocols list is now treated as user-defined disablement of the TLS ALPN extension.
+  Outlier detection (passive health check) is now disabled by default. refer to https://gateway.envoyproxy.io/docs/api/extension_types/#backendtrafficpolicy for working with passive health checks.
   Envoy Gateway treats errors in calls to an extension service as fail-closed by default. Any error returned from the extension server will replace the affected resource with an "Internal Server Error" immediate response. The previous behavior can be enabled by setting the `failOpen` field to `true` in the extension service configuration.
-  Envoy Gateway now return a 500 response when a ClientTrafficPolicy translation fails for HTTP/GRPC routes, and forwards.
-  client traffic to an empty cluster when a ClientTrafficPolicy translation fails for TCP routes.
+  Envoy Gateway now return a 500 response when a ClientTrafficPolicy translation fails for HTTP/GRPC routes, and forwards client traffic to an empty cluster when a ClientTrafficPolicy translation fails for TCP routes.
   Any issues with `EnvoyProxy` reference in a `Gateway` will prevent the Envoy fleet from being created or result in the deletion of an existing Envoy fleet.
   Envoy Gateway now returns a 500 response when a BackendTLSPolicy translation fails for HTTP/GRPC/TLS routes.
 
@@ -37,10 +34,10 @@ new features: |
   Added support for overriding status code in response overrides ClientTrafficPolicy.
   Added support for AllowModeOverride for ext-proc in EnvoyExtensionPolicy.
   Added support for configuring remote JWKS settings with BackendCluster in SecurityPolicy.
-  Added support for infra deployment in the gateway namespace.
   Added support for sending body to Ext-Auth server in SecurityPolicy.
   Added support for Sending attributes to ext-proc in EnvoyExtensionPolicy.
   Added support for configuring hostEnvKeys for Wasm extensions in EnvoyExtensionPolicy.
+  Gateway API Route rule name is propagated to XDS metadata as sectionName.
 
 bug fixes: |
   Fixed a panic in the provider goroutine when the body in the direct response configuration was nil.
@@ -68,7 +65,6 @@ bug fixes: |
   Fixed limitations that prevented creation of FQDN Endpoints with a single-character subdomain in Backend.
   Fixed issue where SecurityContext of shutdown-manager container was not updated by overriding helm values.
   Fixed issue with incorrect IPFamily detection for backends.
-  Gateway API Route rule name is propagated to XDS metadata as sectionName.
 
 # Other notable changes not covered by the above sections.
 Other changes: |

site/content/en/news/releases/notes/v1.3.0-rc.1.md

@@ -7,13 +7,10 @@ Date: January 23, 2025
 
 ## Breaking changes
 - The Container `ports` field of the gateway instance has been removed, which will cause the gateway Pod to be rebuilt when upgrading the version.
-- ClientTrafficPolicy previously treated an empty TLS ALPNProtocols list as being undefined and applied Envoy Gateway defaults.
-- An empty TLS ALPNProtocols list is now treated as user-defined disablement of the TLS ALPN extension.
-- Outlier detection (passive health check) is now disabled by default.
-- refer to https://gateway.envoyproxy.io/docs/api/extension_types/#backendtrafficpolicy for working with passive health checks.
+- ClientTrafficPolicy previously treated an empty TLS ALPNProtocols list as being undefined and applied Envoy Gateway defaults. An empty TLS ALPNProtocols list is now treated as user-defined disablement of the TLS ALPN extension.
+- Outlier detection (passive health check) is now disabled by default. refer to https://gateway.envoyproxy.io/docs/api/extension_types/#backendtrafficpolicy for working with passive health checks.
 - Envoy Gateway treats errors in calls to an extension service as fail-closed by default. Any error returned from the extension server will replace the affected resource with an "Internal Server Error" immediate response. The previous behavior can be enabled by setting the `failOpen` field to `true` in the extension service configuration.
-- Envoy Gateway now return a 500 response when a ClientTrafficPolicy translation fails for HTTP/GRPC routes, and forwards.
-- client traffic to an empty cluster when a ClientTrafficPolicy translation fails for TCP routes.
+- Envoy Gateway now return a 500 response when a ClientTrafficPolicy translation fails for HTTP/GRPC routes, and forwards client traffic to an empty cluster when a ClientTrafficPolicy translation fails for TCP routes.
 - Any issues with `EnvoyProxy` reference in a `Gateway` will prevent the Envoy fleet from being created or result in the deletion of an existing Envoy fleet.
 - Envoy Gateway now returns a 500 response when a BackendTLSPolicy translation fails for HTTP/GRPC/TLS routes.
 
@@ -39,10 +36,10 @@ Date: January 23, 2025
 - Added support for overriding status code in response overrides ClientTrafficPolicy.
 - Added support for AllowModeOverride for ext-proc in EnvoyExtensionPolicy.
 - Added support for configuring remote JWKS settings with BackendCluster in SecurityPolicy.
-- Added support for infra deployment in the gateway namespace.
 - Added support for sending body to Ext-Auth server in SecurityPolicy.
 - Added support for Sending attributes to ext-proc in EnvoyExtensionPolicy.
 - Added support for configuring hostEnvKeys for Wasm extensions in EnvoyExtensionPolicy.
+- Gateway API Route rule name is propagated to XDS metadata as sectionName.
 
 ## Bug fixes
 - Fixed a panic in the provider goroutine when the body in the direct response configuration was nil.
@@ -70,7 +67,6 @@ Date: January 23, 2025
 - Fixed limitations that prevented creation of FQDN Endpoints with a single-character subdomain in Backend.
 - Fixed issue where SecurityContext of shutdown-manager container was not updated by overriding helm values.
 - Fixed issue with incorrect IPFamily detection for backends.
-- Gateway API Route rule name is propagated to XDS metadata as sectionName.
 
 ## Other changes
 - Bumped Gateway API to v1.2.1.