homelab VS k9s

K3s is great, I use it on all of my personal clusters (here and here). It's lightweight and very easy to manage.

https://github.com/khuedoan/homelab if you haven't come across it yet. To add to your bookmarks.

I have my Kubernetes homelab public on GitHub, everything is automated and defined as code. Hope it will help you get started and see what's possible.

So I 've got inspired by https://github.com/khuedoan/homelab and initially after lurking this sub for a while I came up with a plan to consider some of these solutions: - openmediavault as a VM to use 2x4TB /w ext4 & mergerFS or TrueNAS in RAID1 - I think mergerFS gives more options to increase storage with extra drives later, but I don't plan to hoard lots of data. Also rather opted for tiered cache via SSD to save some power but if such lot of VMs would write this would work? - nextcloud VM to easiely manage files via browser and have mobile app sync for photos with some kind of gallery plugins etc - I think this may be optional if there's other solution as nextcloud seems to not be light. Or something like Seafile would be enough? - kubernetes - k3s/microk8s single VM node or 2 VM nodes - would I need more? and so - can then openmediavault be used as a storage for it like TrueNAS? - Rancher - if used k3s - I quite liked the UI of rancher desktop, more than portainer when I tried with microk8s, but I don't pass on using something else, eg. Lens - Gitea - for hosting code - tekton / teamcity - for running tests and commit build hooks - fluxCD / argoCD - for deploying builds to kubernetes

khuedoan/homelab

Here's my project (running on 4 mini PC) that I'm using for learning and self-hosting https://github.com/khuedoan/homelab, it's fully automated from empty disk to operating services.

You can checkout my repo If you'd like to do the same for your homelab (it's also modular so you can just use the OS installation part)

Here're the links to the Markdown source and the web view.

You can checkout my Kubernetes homelab, it's fully automated from empty disk, very customizable and extensible.

You can view the code here: https://github.com/khuedoan/homelab (the ./metal folder)

Pierre: The first tool I recommend is K9s. It's not just a time-saver but a productivity booster. With its intuitive interface, you can speed up all the usual kubectl commands, access logs, edit resources and configurations, and more. It's like having a personal assistant for your cluster management tasks.

The last thing you really need is a common set of tools that you want fingertip access to. I really commonly use LazyGit and K9s in my day job so those are the tools I will show off in this article.

K9s is your best friend (get it? 🐶) when exploring your cluster via the terminal. It shares commonality with Vim for its interaction style using shortcuts and starting commands with: but don’t let that discourage you. K9s keeps a vigilant eye on Kubernetes activities, providing real-time information and intuitive commands for resource interaction.

k9s: brew install k9s

I would like to put in a vote for k9s, which is also on the list at Terminal Trove. [0] It's the most convenient tool I've ever found for Kubernetes management. Based on that experience I'll definitely be checking out Harlequin.

[0] https://k9scli.io/

$ wget https://github.com/derailed/k9s/releases/download/v0.29.1/k9s_Darwin_amd64.tar.gz $ tar -xzf k9s_Darwin_amd64.tar.gz $ sudo mv k9s /usr/local/bin/

All in all, run things, do some kubectl apply -f something.yml every day, install k9s, and try to configure a big one cluster at some point.

(K9s is one of my favorite tools for navigating Kubernetes clusters through the CLI).

K9s is an open-source, terminal-based UI for interacting with your Kubernetes clusters, making navigating, observing, and managing your apps easier. If you use Kubectl but wish it was easier and faster to use, K9s might be just what you're looking for!

k9s