Learning about the #indieweb movement has been one of the most interesting byproducts of joining Mastodon earlier this year. I particularly liked this talk transcript by Jamie Tanna as an introduction to the topic:
https://www.jvt.me/posts/2019/10/20/indieweb-talk/
When running Kubernetes on a cloud provider, rather than locally using minikube, it’s useful to know which node a pod is running on.
The normal command to list pods doesn’t contain this information:
$ kubectl get pod NAME READY STATUS RESTARTS AGE neo4j-core-0 1/1 Running 0 6m neo4j-core-1 1/1 Running 0 6m neo4j-core-2 1/1 Running 0 2m I spent a while searching for a command that I could use before I came across Ta-Ching Chen’s blog post while looking for something else.
You wouldn't get this problem with Linux 😊
https://www.theguardian.com/australia-news/article/2024/jul/19/microsoft-windows-pcs-outage-blue-screen-of-death
You would of course, get many other problems 🙃