Notes

A green Ready status and a correct node configuration are not the same guarantee. I ran into that distinction while standardizing kubelet settings across several node classes in a Kubernetes cluster I operated. Each class had a configuration baseline stored in Git. It defined resource reservations, eviction thresholds, and image garbage collection settings. Kubernetes reported the nodes as Ready, yet a separate check found that the local /var/lib/kubelet/config.yaml on some of them no longer matched the expected file. ...

How a final newline differs from a blank line and why one byte affects git diff and git blame.

Why AGENTS.md should be seen not only as AI instructions, but also as part of a DocOps approach to engineering context.

Why AGENTS.md should stay short and not replace README, ADR, CHANGELOG, or project documentation.

Why AGENTS.md is useful not only for AI, but also for returning to a project after some time.

Which sections to keep in AGENTS.md so AI can understand the project quickly without turning it into another README.

Why I keep AI agent instructions in the repository and how AGENTS.md helps preserve project context.

Troubleshooting an unstable Kubernetes node caused by an exhausted inotify watchers limit.

An overview of the processes that consume inotify watchers and why this Linux limit should be part of infrastructure capacity planning.