@sheogorath Are you still using OpenShift for your K8S cluster?

@mhamzahkhan No, nowadays I use plain kubernetes. I tried to use OKD on hetzner, this went south on every update due to concerning fsync times (around 2 seconds) in etcd. And overall, it simply shipped some stuff, that I didn't consider needed for my home setup.

Therefore I went for plain K8s on baremetal using kubeadm at home. It's all based Fedora 35 currently (not even CoreOS), but so far, it works quite well :)

@mhamzahkhan Given that I use(d) the Fedora packages for Kubernetes in order to get all SELinux thing working properly, I hit a bit of a limit regard Kubernetes versions. And since the maintainer of the existing package, didn't have time to update stuff, I run effectively a fork of the official kubernetes packages on COPR.

(Technically speaking, I only need kubelet and kubeadm, since the rest is containerised, and maybe kubectl, but still :D)

@sheogorath Ah! Interesting.
I want to rebuild my K8S clusters because at the moment they are a bit of a mess.
I was considering OKD. I've used OpenShift a very long time ago for a short time. I liked it, but from memory (no pun intended), it ate up all my RAM. I have a bit more RAM to spare now.

At the moment, I'm using plain K8S on bare metal, using FCOS and Kubespray to deploy it. It works well, but I've had problems with upgrades in the past.


Yes, OpenShift is not easy on memory. Also one reason to not run it.

My system and Kubernetes updates are done using the system-upgrades-controller from rancher. It's not perfect and there are some potential race conditions, but overall, I'm quite happy.

My Kubernetes updates work like this:

System upgrades like this:

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!