fhernandezn
commented
1 month ago I'm facing the same problem with a use case in my company. ACLs can be even affected by typos or so and don't want some machines to be able to access others due to legal/contractual clauses. I also don't want to purchase different domains just to solve this
adyekjaer
What are you trying to do?
I have a few different networks that under no circumstance do I want them to have an access to each other, and I want to be able to access those networks using Tailscale (one at a time). Using ACLs to do so is not an option because ACLs might be error-prone and someone might connect those environment by a mistake one day. Separating to different accounts is much safer in that regard.
How should we solve this?
The ability to create multiple networks / sub-accounts under one Tailscale domain/account.
What is the impact of not solving this?
Currently I can not use Tailscale for that use-case although the product is great and has tons of features that I really need (for example the Kubernetes operator).
Anything else?
No response