From 1d388759ad55168b68d3102f3274ad82c4169c08 Mon Sep 17 00:00:00 2001 From: Arko Dasgupta Date: Wed, 8 Oct 2025 12:51:08 -0700 Subject: [PATCH] delay migrating to XDS Name Scheme V2 by default The cost of migrating envoy patch policies to the new naming scheme is higher than the impact of staying on the V1 scheme Signed-off-by: Arko Dasgupta --- .../en/latest/tasks/extensibility/envoy-patch-policy.md | 4 ++-- site/content/en/news/releases/v1.5.md | 4 ++-- .../content/en/v1.5/tasks/extensibility/envoy-patch-policy.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/site/content/en/latest/tasks/extensibility/envoy-patch-policy.md b/site/content/en/latest/tasks/extensibility/envoy-patch-policy.md index 72b047e3bc4..41f6a125091 100644 --- a/site/content/en/latest/tasks/extensibility/envoy-patch-policy.md +++ b/site/content/en/latest/tasks/extensibility/envoy-patch-policy.md @@ -104,9 +104,9 @@ Because [EnvoyPatchPolicy][] relies on specific xDS resource names, it’s impor | | V2 (HTTPS) | `https-` | `https-443` | -This change is gated by the XDSNameSchemeV2 runtime flag. The flag is disabled by default in v1.5 and will be enabled by default starting in v1.6. +This change is gated by the XDSNameSchemeV2 runtime flag. The flag is disabled by default in v1.5 and will be enabled by default in a future release. -We recommend users begin migrating their [EnvoyPatchPolicy][] resources to use the version 2 naming scheme before upgrading to v1.6. +We recommend users begin migrating their [EnvoyPatchPolicy][] resources to use the version 2 naming scheme. To opt in to the new naming scheme early, add the`XDSNameSchemeV2` runtime flag to the `runtimeFlags.enabled` field in your [EnvoyGateway][] configuration. diff --git a/site/content/en/news/releases/v1.5.md b/site/content/en/news/releases/v1.5.md index 6cd2bb415cc..4612fbcaae1 100644 --- a/site/content/en/news/releases/v1.5.md +++ b/site/content/en/news/releases/v1.5.md @@ -27,7 +27,7 @@ Envoy Gateway v1.5.0 introduces powerful enhancements, resolves critical issues, - **Endpoint Removal Behavior**: Endpoints absent from service discovery are removed even if their active health checks succeed. - **xDS Listener Naming**: Listeners are now named based on listening port and protocol instead of Gateway and section names. - This affects existing `EnvoyPatchPolicies` and `ExtensionManagers`. - - Controlled by the `XDSNameSchemeV2` runtime flag (disabled in v1.5, enabled in v1.6). + - Controlled by the `XDSNameSchemeV2` runtime flag (disabled by default). - See the [migration guide](../../v1.5/tasks/extensibility/envoy-patch-policy#xds-name-scheme-v2) to prepare. - **Metrics Label Change**: Removed `xds-translator` and `xds-server` values from the `runner` label in `watchable_subscribe_total`; use `xds` instead. - **ALS Access Loggers**: ALS now has HTTP/2 enabled on the cluster by default. @@ -134,4 +134,4 @@ We encourage all users to upgrade to v1.5.0 to take advantage of the new feature [Release Notes]: ./notes/v1.5.0.md [docs]: https://gateway.envoyproxy.io [matrix]: https://gateway.envoyproxy.io/news/releases/matrix/ -[Install]: https://gateway.envoyproxy.io/docs/tasks/quickstart/ \ No newline at end of file +[Install]: https://gateway.envoyproxy.io/docs/tasks/quickstart/ diff --git a/site/content/en/v1.5/tasks/extensibility/envoy-patch-policy.md b/site/content/en/v1.5/tasks/extensibility/envoy-patch-policy.md index 72b047e3bc4..41f6a125091 100644 --- a/site/content/en/v1.5/tasks/extensibility/envoy-patch-policy.md +++ b/site/content/en/v1.5/tasks/extensibility/envoy-patch-policy.md @@ -104,9 +104,9 @@ Because [EnvoyPatchPolicy][] relies on specific xDS resource names, it’s impor | | V2 (HTTPS) | `https-` | `https-443` | -This change is gated by the XDSNameSchemeV2 runtime flag. The flag is disabled by default in v1.5 and will be enabled by default starting in v1.6. +This change is gated by the XDSNameSchemeV2 runtime flag. The flag is disabled by default in v1.5 and will be enabled by default in a future release. -We recommend users begin migrating their [EnvoyPatchPolicy][] resources to use the version 2 naming scheme before upgrading to v1.6. +We recommend users begin migrating their [EnvoyPatchPolicy][] resources to use the version 2 naming scheme. To opt in to the new naming scheme early, add the`XDSNameSchemeV2` runtime flag to the `runtimeFlags.enabled` field in your [EnvoyGateway][] configuration.