My urgent, drop-everything, “bad actors have access to merchants and we can’t block them!” ticket that I rushed to finish didn’t make it into the release. It passed QA; everything works. There’s no complaints on code quality, either.

The blocker? My code uses the word “whitelist” (which is already present in the greater codebase in a related feature), and that made the woke VP (who happened to review the ticket) go REEEEEEE!! and demand I fix it to use approved language, therefore delaying the security fix until the next release cycle.

Yes, seriously.
It would be comical if I wasn’t so disgusted.

Oh well. Enjoy your bad company PR, dude. I hope it all burns.

## Learning k8s

Okay, that's kind of obvious, I just have no idea why I didn't think of it..

I've made a cluster out of a rpi, a i7 PC and a dell xps lappy. Lappy is a master and the other two are worker nodes.

I've noticed that the rpi tends to hardly ever run any of my pods. It's only got 3 of them assigned and neither of them work. They all say: "Back-off restarting failed container" as a sole message in pod's description and the log only says 'standard_init_linux.go:211: exec user process caused "exec format error"' - also the only entry.

Tried running the same image locally on the XPS, via docker run -- works flawlessly (apart from being detached from the cluster of other instances).

Tried to redeploy k8s.yaml -- still raspberry keeps failing.

wtf...

And then it came to me. Wait.. You idiot.. Now ssh to that rpi and run that container manually. Et voila! "docker: no matching manifest for linux/arm/v7 in the manifest list entries."

IDK whether it's lack of sleep or what, but I have missed the obvious -- while docker IS cross-platform, it's not a VM and it does not change the instructions' set supported by the node's cpu. Effectively meaning that the dockerized app is not guaranteed to work on any platform there is!

Shit. I'll have to assemble my own image I guess. It sucks, since I'll have to use CentOS, which is oh-so-heavy compared to Alpine :( Since one of the dependencies does not run well there..

Shit.

Learning k8s is sometimes so frustrating :)