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

join a local server/agent to a remote server #439

Closed
webcoderz opened this issue Aug 8, 2024 · 2 comments
Closed

join a local server/agent to a remote server #439

webcoderz opened this issue Aug 8, 2024 · 2 comments

Comments

@webcoderz
Copy link

i am failing to understand if this is possible , i have a local gpu node i want to connect to a remote DO server , is this possible? if so, do you have a reference to an example of how its done?

@alexellis
Copy link
Owner

Hi @webcoderz this is really a question for the k3s project, not for k3sup.

You will find details about k3s networking here: https://docs.k3s.io/networking/basic-network-options

If you want to invoke a HTTP or TCP webservice hosted on the local server, the easiest way to do this would be using an inlets tunnel: https://inlets.dev/blog/2024/06/06/tunnel-k8s-via-aws-ec2.html

If you don't want to expose the service to the Internet from the local K3s cluster, then you can also do a "private tunnel" where only the control plane is public, and the data plane is accessed within the remote cluster via ClusterIP.. we have details on that if you're interested ask on the inlets Discord once you sign up.

Alex

Repository owner locked as resolved and limited conversation to collaborators Aug 9, 2024
@alexellis
Copy link
Owner

I took a couple of hours to write-up how to do what you want with inlets: https://inlets.dev/blog/2024/08/09/local-ollama-tunnel-k3s.html

If you want more versatility, deploying OpenFaaS locally would make sense, then you can orchestrate and invoke the code using the GPU remotely via HTTP/REST.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants