let's see if I can self-host gitpod over the weekend (starting now!)

https://www.gitpod.io/docs/self-hosted/latest/cluster-set-up/on-k3s

K3s Cluster for Gitpod Self-Hosted

Explore the documentation to learn more about Gitpod.io and Gitpod Self-Hosted.

my node has been tainted

ok continuing last attempt of installing k3s after a good night sleep and a brunch.

I managed to install the master node with 644 permission /yay/ after I realized I was not using the correct flag, after that I tried 2x but forget to re-load my .bashrc lol >.>

and I thought I have every *dependencies* out there, but it seems this "container runtime" is missing
ok this is ridiculous
I hate canonical but should I give in

context: it seems the `iptables` on debian is not compatible with k3s:

https://andrewmunro.me/posts/2021/08/creating-a-k3s-cluster-on-debian-11-bullseye-step-1-provision/

will try out the "workaround"

Creating a K3S Cluster on Debian 11 Bullseye (Step 1: Provision) //andrew.munro

A blog about software, professionalism, and everything between.

I agree andrew
I need to remove my tendency to create random image for everything that I do but I can't
I don't know what the heck is you but goodbye! (it probably has something with the "old" iptables that I remove)
I'm glad that linode has a "clone vm" option so I don't need to repeat these steps
dead
let's see if rebooting fixes this
while I'm rebooting, I'm wondering if pop_os server is actually a thing

LOL I just realized that I need to use calico CNI instead of the default, and, in fact, I had actually copied the env file with --flannel-backend=none to disable to default CNI 😂

I really think I should've read the code first before copying 🤡 but meh, who read the code they're about to copy blindly /s

ok it's running now (still got one error but... progress)
it was YAML

progress: need to change hostname on both machine (I think), because agent node "kind of" connect but not really connected since I assume their hostname are the same (?)

but calico is behaving weirdly so I need to redo it all over again

FINALLY succeeded in setting up 2-node k3s cluster with a different server 😀 🎉