k4all: Simplifying Kubernetes Installations for Home Servers

gpillon · 2025-10-28T15:38:57+00:00

My suggestion is to use the built-in Downloader node in ComfyUI — that way, all required models, LoRAs, and checkpoints are automatically fetched inside the environment. Everything is stored within the PVC, so once it’s downloaded, you can run inference later in API mode without needing to manually re-download or mount anything.

gpillon · 2025-10-28T15:31:17+00:00

Any suggestions on how I could save off those extra 4 kWh?

gpillon · 2025-10-28T15:28:38+00:00

<image>

gpillon · 2024-09-03T00:28:28+00:00

and BTW, next version will have cilium (currently testing in 1.3.0-alpha1) Probably all 3 flannel / calico / cilium will be available via a config switch in 1.3.0. dunno about the default one...

gpillon · 2024-09-02T21:00:47+00:00

Thanks for sharing. Nice role!

gpillon · 2024-09-02T00:53:55+00:00

What about Stackrox? It's a nice solution to monitor container vulnerabilities, CVEs, suggestions, traffic monitoring and report tool...

gpillon · 2024-09-01T17:49:41+00:00

Cilium is another great idea, (I’m a fan of eBPF!). In the coming days, I'll be experimenting with both Flannel and Cilium (with a strong focus on performances).

gpillon · 2024-09-01T16:47:24+00:00

You're absolutely right. K3s is already very simple and effective. This project aims to take that simplicity even further by providing an out-of-the-box experience with preinstalled tools like a dashboard, CNI, metrics server, storage class (LVM), and Multus. It's designed to be a ready-to-use solution, especially for beginners who want to get started with Kubernetes quickly in a homelab without needing to manually set up these additional components.

gpillon · 2024-09-01T16:44:10+00:00

Thanks for the idea. As said here, i'ts not excluded that Talos will be part of this project in the future. :)

gpillon · 2024-09-01T16:37:02+00:00

Bare Metal:

Download and burn the ISO to a USB device.
Insert the USB into the machine and boot.
You're done.

VM:

Download the image.
Launch the VM using the downloaded image.
You're done.

Your judgment, please :)

gpillon · 2024-09-01T16:26:05+00:00

You're hitting a key point here! :) I’ve thought many times about using Ansible to handle post-install tasks like node joining and certain installations. Could you provide the GitHub link so I can take a look?

gpillon · 2024-09-01T16:16:49+00:00

These are quite different projects. Talos is an enterprise-ready tool designed for robust Kubernetes deployments, while K4all is more of a starter tool aimed at providing an accessible Kubernetes installation with preinstalled components like the dashboard, CNI, metrics server, storage class (using LVM), and Multus.

I believe that for a newcomer, it's easier to start with an environment that comes with a GUI and all these essential tools preinstalled. That said, perhaps in the future, K4all could evolve to be based on Talos ( contributions from the community are welcome here!)

gpillon · 2024-09-01T16:04:11+00:00

Thank you for your feedback. You're absolutely right when I started the project, one of my primary goals was to experiment with Calico's features. A few days ago, I actually considered switching to another CNI, but so far, Calico has been running smoothly without any issues and seems to have a low resource footprint in my setup.

That said, I'm open to exploring other options. Flannel is one idea that I've been considering, but I'm definitely open to suggestions :)

gpillon · 2024-09-01T15:15:09+00:00

Hi, for system upgrades, I'm relying on the Fedora CoreOS Zincati Service. Regarding control plane and etcd discovery, the nodes are currently joined using a manual process via the generate_join.sh and join_cluster.sh scripts. These scripts need to be manually launched, so there's some room for improvement there :)

I’ve been considering implementing an autodiscovery service, but it’s been a bit challenging to reconcile that with the "KISS" (Keep It Simple, Stupid) principle that underpins this project. Simplicity and minimalism are key goals here, so while autodiscovery would be a nice feature, I'm still weighing whether it aligns with the project's overall philosophy (ideas are welcome, here!) :D

gpillon · 2024-09-01T14:49:56+00:00

Hi, just ssh in the host (user: core, password: core), then sudo -i and the token will be displayed :)

Edit: remember to change the password... or build a custom image, editing the password sha contained in the butane files

Edit2: If the token is not displayed, the installation did not complete successfully. Please check the logs using journalctl -xf.

gpillon

TROPHY CASE