Skip to content

Add client.acceptRoutes option for in-cluster client#28

Merged
kervel merged 1 commit intomainfrom
feature/client-accept-routes
Feb 26, 2026
Merged

Add client.acceptRoutes option for in-cluster client#28
kervel merged 1 commit intomainfrom
feature/client-accept-routes

Conversation

@kervel
Copy link
Copy Markdown
Contributor

@kervel kervel commented Feb 26, 2026

Summary

  • Add client.acceptRoutes value to control the --accept-routes flag on the in-cluster tailscale client

Use case

When other nodes on the tailnet advertise subnet routes, the in-cluster client needs --accept-routes=true to use them. Without this option there was no way to enable it through values.

Changes

  • values.yaml: New client.acceptRoutes field (default "unset", same pattern as acceptDns)
  • values.schema.json: Schema entry accepting string or boolean
  • client-deployment.yaml: Conditional --accept-routes flag in tailscale up

Test plan

  • helm lint passes
  • --accept-routes absent when acceptRoutes: "unset" (default)
  • --accept-routes=true rendered when acceptRoutes: true
  • --accept-routes=false rendered when acceptRoutes: false

🤖 Generated with Claude Code

Allow controlling the --accept-routes flag on the tailscale client,
following the same "unset" default pattern as acceptDns. When set to
true, the in-cluster client accepts subnet routes advertised by other
nodes on the tailnet.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kervel kervel merged commit c6f4915 into main Feb 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant