home.social

#k0s — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #k0s, aggregated by home.social.

  1. I need #Mirantis' #k0s to get a little more popular so k3s/Rancher keep having good friendly competition.

  2. The k0s project has community office hours today 14:00 CEST on zoom. Feel free to join if you want talk with the k0s team.

    dateful.com/eventlink/27359197

  3. We know #TalosLinux is 🤏 but is it really the smallest?

    We ran the tests. We’ve got the data. Check it out if you like numbers.

    Watch → youtu.be/atPvnJMGdfs
    Read → siderolabs.com/blog/which-kube

    #Kubeadm #K3s #K0s #Kairos #RKE2 #Kubernetes #K8s

  4. 🆕 The Cloud Native Computing Foundation (#CNCF) has welcomed #k0s into its Sandbox program!

    k0s - a lightweight, zero-friction Kubernetes distribution - has been gaining adoption in edge computing and resource-constrained environments, and it now joins fellow lightweight distribution k3s in the Sandbox.

    Dive deeper: bit.ly/3HoLWhV

    #InfoQ #Kubernetes #CloudNative #EdgeComputing #DevOps

  5. I now have a tiny #Kubernetes to play with. I'm using #k0s with one controller VM and two workers, one VM and one bare metal, all running on Debian.

    So far I installed cilium (although I'm not sure why I did that, tbh) and set up democratic-csi such that I can create PersistentVolumeClaims on my big ZFS array over NFSv4.

    I think my next step is to install the #Tailscale operator and actually spin up a service.

    Everything has "test" in the name so probably after I get a service running I'll tear it all down and make a for-realsies cluster.

    #HomeLab #SelfHosted

  6. So I managed to get #Forgejo jobs running in a way that I'm happy enough with. The main concern is that they're isolated as possible. The current runner has a scary warning on it that it's in alpha and shouldn't be considered secure.

    The runner instance is Debian running in an #lxd --vm on my laptop (I didn't want to consume resources on the server since it's small). In this instance I have #k0s running, which is a slimmed down #Kubernetes, which is running #Codeberg 's runner pod. This has three containers. One to register the runner, then two others that are always running, the runner itself and #Docker -in-Docker . You can replicate this entire setup so that each runner gets its own DinD which is completely separated from the others.

    Each runner checks for a single job in a loop, and once a job is completed then the docker server is pruned, and the runner shuts down. Then k0s will automatically restart it. This isn't perfect but it's better than runner processes which never shut down, because the docker cache will linger and others can look at it to spy on your jobs.

  7. Deployed the first user-facing service to cons.town's kubernetes cluster:
    hello.cons.town

    The cool thing about the cluster that it's deployed delcaratively with Guix. metallb used for making services available outside of kubernetes. cert-manager for certificates management and nginx-ingress for tls termination.

    Anything else cool I forget to mention?

  8. Fully-declarative deployment of 2-nodes Kubernetes cluster :kubernetes: successfully done with Guix :guix:!

    The only manual step was generating a worker token to connect a worker kubernetes node to the controller and copying it to the respective host. It can be automated, but not today.

    Check out the source code: cons.town

    Imagine, what kind of fun we can have with it now?

  9. @bagder looks like the CFP is not open yet.

    I wonder if something or /#kubernetes would be of interest for this event

  10. Trying to deploy kubernetes cluster with Guix.

    guix deploy fails multiple times in different ways :/

    The most annoying part that it somehow makes ssh daemon to stop responding, so I have to restart VPS after such occasions. Also, the deploy of 0-diff system is very slow for some reason.

    Another funny observation: shepherd doesn't respond to `herd status` during guix deploy.

    Definitely need to find out why it happens, but today goal is to get k8s cluster running.

  11. Next week I'm open for another community pair programming session.

    It's a nice opportunity to exchange knowledge, gather feedback and progress on a awaiting tasks.

    There are three topics:
    - Interactive development with Guile :: [n]REPLs, . What we can borrow from , ?

    - Guile Testing Framework :: srfi-64, clojure.test, kaocha for guile.

    - Guix-based DevOps :: , , , deploy.

    Ping me if you want to work and brainshtorm on some of topics above.

  12. Decided to avoid HashiCorp Nomad and go with k0s on top of Guix System.

    The nomad's community is much smaller than kubernetes', probably so small that they didn't even fork the project after license change.

    License is a actually a big deal. Source available software is a bit better than proprietary, but still very far from FOSS. The company potentially going bananas is only one of many problems.

  13. TIL about k0s - "The Zero Friction Kubernetes"

    This looks like they've automated/simplified much of the k8s cluster creation process, especially if you want a small scale lab environment.

    docs.k0sproject.io/stable/

    #homelab #kubernetes #k0s #k8s

  14. Would you like to meet the k0s team? There is an opportunity tomorrow to ask all the questions you have, give feedback, request features etc.

    Join us on zoom!

    dateful.com/eventlink/27359197

  15. @telnetlocalhost I decided that for now I will stick with the good ol' #docker and docker-compose, just decided to clean it up a bit codeberg.org/fourstepper/ansib. Only thing left to do is figure out how to auto-deploy on push to a different repository (probably woodpecker-ci.org/plugins/Trig)

    The next natural step seems to be #k0s - I played around with the k0sctl yesterday, which is used to bootstrap clusters, and I really like that k0s has almost no opinions - just runs a barebones Kubernetes cluster!

  16. I really need to check out #Mirantis #k0s. Seems similar to the things I also like about #k3s. #Kubernetes