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

Tailscale strategy #219

Open
utkuozdemir opened this issue Apr 27, 2023 · 2 comments
Open

Tailscale strategy #219

utkuozdemir opened this issue Apr 27, 2023 · 2 comments

Comments

@utkuozdemir
Copy link
Owner

Add a new strategy: tailscale

User provides a tailscale api key or sth like that. We run sidecars on each side and use tailscale network to do the rsync. This way we might be able to get through the most difficult network setups.

@CaelFrost
Copy link

CaelFrost commented Sep 5, 2024

One way to dip a toe in on this goal might be allowing
loadBalancerClass: tailscale

to be added to the svc and then having the tailscale operator do the work of assigning the ip to the load balancer service.

https://leebriggs.co.uk/blog/2024/02/26/cheap-kubernetes-loadbalancers

i followed this guide, while attempting to use it for pv-migrate, but sadly wasnt able to complete it because the spec.loadBalancerClass property is immutable, and i was unable to find a way to influence how pv-migrate creates it.

@utkuozdemir
Copy link
Owner Author

Ah, this is a great idea, it just needs the setup on the cluster to support that (have the operator).

As I remember there is no way to override loadBalancerClass atm, but it can be added without too much trouble I believe (as a helm value).

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