diff options
| author | Simon Law <sfllaw@tailscale.com> | 2025-11-25 09:21:55 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-11-25 09:21:55 -0800 |
| commit | 848978e664aebb28e86c17bdad4b048f981079df (patch) | |
| tree | 8724a1ea5b883bda9b57f3c6abaa960643a267df /util/execqueue/execqueue.go | |
| parent | 7073f246d3e94a849d20420eaff69d7be7e494b7 (diff) | |
| download | tailscale-848978e664aebb28e86c17bdad4b048f981079df.tar.xz tailscale-848978e664aebb28e86c17bdad4b048f981079df.zip | |
ipn/ipnlocal: test traffic-steering when feature is not enabled (#17997)
In PR tailscale/corp#34401, the `traffic-steering` feature flag does
not automatically enable traffic steering for all nodes. Instead, an
admin must add the `traffic-steering` node attribute to each client
node that they want opted-in.
For backwards compatibility with older clients, tailscale/corp#34401
strips out the `traffic-steering` node attribute if the feature flag
is not enabled, even if it is set in the policy file. This lets us
safely disable the feature flag.
This PR adds a missing test case for suggested exit nodes that have no
priority.
Updates tailscale/corp#34399
Signed-off-by: Simon Law <sfllaw@tailscale.com>
Diffstat (limited to 'util/execqueue/execqueue.go')
0 files changed, 0 insertions, 0 deletions
