Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Install tailscale and k3s on the master node and worker nodes. I have a setup like this and it works well. I have nodes in different physical locations from the master node, it works fine.
Do you have a guide or any documentation to help me and my buddy out, like I said I can post logs later if that would be helpful?
Other than k3s.io’s documentation and tailscale’s documentation, I don’t have any to share, but I don’t mind answering questions if you are stuck.
https://docs.k3s.io/installation https://tailscale.com/kb/1017/install
I will also mention that we are setting this up with x86_64 architectures and arm if that matters.
Should probably move that info to the main post.
I have mixed architecture cluster as well. It works great as long as you set your manifests up properly and either use public images that support both or you build your own, or you set up node affinity to ensure the architecture-specific pod runs only on the node with the correct architecture.