Skip to content

delay migrating to XDS Name Scheme V2 by default #7170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

delay migrating to XDS Name Scheme V2 by default #7170

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions site/content/en/latest/tasks/extensibility/envoy-patch-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,9 +104,9 @@ Because [EnvoyPatchPolicy][] relies on specific xDS resource names, it’s impor
| | V2 (HTTPS) | `https-<Port>` | `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.

Expand Down
4 changes: 2 additions & 2 deletions site/content/en/news/releases/v1.5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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/
[Install]: https://gateway.envoyproxy.io/docs/tasks/quickstart/
4 changes: 2 additions & 2 deletions site/content/en/v1.5/tasks/extensibility/envoy-patch-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,9 +104,9 @@ Because [EnvoyPatchPolicy][] relies on specific xDS resource names, it’s impor
| | V2 (HTTPS) | `https-<Port>` | `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.

Expand Down
Loading