Skip to content
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.

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

[Feature] Ability to not configure egress route on node #3320

Open
RomLecat opened this issue Feb 8, 2025 · 2 comments
Open

[Feature] Ability to not configure egress route on node #3320

RomLecat opened this issue Feb 8, 2025 · 2 comments

Comments

@RomLecat
Copy link

RomLecat commented Feb 8, 2025

Hello,

I have a Netmaker cluster with some hosts, which is only used for administration purposes.
The clusters use more "traditional" VPNs and/or VPC peering on Cloud for production traffic.

The main issue is that Netmaker VMs automatically import routes defined in egress and there's seems to be no way of not inserting them, so the traffic always uses Netmaker.
A knob in netclient to not configure Netmaker egress routes automatically would be great, very much like running Tailscale without "accept-routes" parameter (https://tailscale.com/kb/1019/subnets#use-your-subnet-routes-from-other-devices).

Thanks!

@abhishek9686
Copy link
Member

abhishek9686 commented Feb 8, 2025

@RomLecat we will soon have access controls for egress routes, where you can control which machines can get these routes applied

@RomLecat
Copy link
Author

RomLecat commented Feb 9, 2025

@abhishek9686 Thanks, that sounds great!
Do you have an idea of the version on which this would be released ?

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

No branches or pull requests

2 participants