VADOSWARE

Want to wait for some Kubernetes resources and don't want to write a full reconciliation loop/operator? Here's how to hack it.

You may not need Flux/ArgoCD or any fancy automated reconciliation loop deployment process just yet! Plain old CI runners work quite well for simple automated deployments (this approach powers this blog right now!).

I finish up the benchmarking process, and share the results. If you want to find what I actually end up using, the answer is in here!

I describe in detail the YAML and Makefile scripts that power the fio and pgbench based tests that will run on every storage provider I managed to set up

I install even more storage providers -- this time OpenEBS cStor, Jiva, LocalPV hostPath, LocalPV ZFS and LINSTOR

I start installing storage plugins, this time Rook (Ceph) -- which takes a while -- and OpenEBS Mayastor. Read this if you want to read a feel-good underdog system administration story.

Part 1 of my second crack at benchmarking storage providers that scale from hobbyist to enterprise. In this post I go over the setup (the code isn't public just yet) of the dedicated servers I'll be using

Kubernetes upgrade sunday -- A series of posts where I do some maintenance and upgrades on my k8s cluster that sometimes happens on a sunday. This sunday I work on node local DNS caching, kube-router, jaeger, cert-manager, traefik, and containerd

Service to service communication broke down due to old Kubeconfig being fed to my old version of kube-router.

I run a small experiment to figure out what the optimal setting is for pm2.