I managed to avoid #Kubernetes for 10 years, but it’s finally caught up to me, so I hope I’m a Kubernetes god after going through all this required (by job) Kubernetes training.
As my old NUC was showing its age, and didn't suffice for my #homelab needs anymore, I decided to build a new one. And because I prefer running all my #selfhosted in containers, but abhor fucking around with #docker and docker-compose, it's a single-node #k8s cluster, using #k3s, just like my old server. One big difference is that the new server has a decent amount of drives for storage. I decided to set up #zfs to manage that, and zfs is all it's cracked up to be.
Did anyone try to use #systemd nspawn as OCI runtime with #kubernetes ? Is there some usable guide how to set this easily to try out? #k8s#systemdnspawn
Started importing the last ~70 tweets into #mastodon of my #kubernetes / #k8s home lab/cluster, it's causing some interesting traffic spikes up to 0.5Mbit. Probably because I'm on some relays on top of normal followers. #activitypub is pretty cool!
#Kubernetes/#K8S Q: I've been having an issue all this while I haven't quite been able to tackle. How do I properly mount a #Samba/#SMB/#CIFS share in a #Docker container on Kubernetes?
I definitely don't want a method that does any "pass through" outside of the container such as mounting said share on the Kubernetes node then passing it to the container, since that seems quite hacky and the deployment/pod could easily be reassigned to a different node.
Since quay.io is down, now is a good time to remind tech folks of reimage. You can use it as a helm post-renderer, it'll copy images from the random wilderness into your own OCI registry, and avoid runtime dependence on the likes of quay and dockerhub
Lame phrase, but I'm really going to try to be more active on the fediverse and socially active from an activist standpoint. Too much hate and hurt in the world not to try.
I've hit my first k8s screwup. Trying to delete an erroneous Ceph Rook deployment, and the ceph object store is stuck in "Terminating" status. Consequently, so is the Namespace it's in, and the CRD which defines it, and so is the entire Rook cluster.
What's the "I don't fucking care, kill it!" command in Kubernetes? "delete --force" doesn't seem to be it...
Oh cloud, it's bigger
It's bigger so you
Use Kubernetes
The lengths admin will go to
To scale their enterprise
Oh no I've said too much
I set it up
That's me in the Docker
That's me on the cloud host
Learning Kubernetes
Trying to launch my apps on you
And I don't know if I can do it
Oh no I've said too much
I haven't set it up
Question for those who do most of their local development on #macOS with an arm64 processor (M1+): What's your preferred approach to running #docker (docker-compose) and/or #kubernetes?
· Official Docker Mac App
· Linux using UTM
· Lima
· Podman
· Other?