kubernetes

Why a successful GitOps flow does not prove publication, and how checking the expected revision ties a release to the site response.

How a public draft helps reconstruct a causal chain, expose hidden dependencies, and define the guarantees of an engineering solution.

How an article moves through two repositories, where CI ends, and which part of delivery belongs to Flux.

Why CI does not block Flux after a direct push, and how a Merge Request with required checks moves validation before the watched branch.

How to turn ticket histories and chat discussions into documentation, checks, and automation that engineers can reuse.

An authorization error from kubectl exec often looks illogical: cannot create resource "pods/exec" The Pod already exists. The command does not create another Pod or modify its specification. get or update might therefore seem like the expected permission, but Kubernetes checks for create. The reason is that RBAC describes Kubernetes API operations, not the literal meaning of kubectl commands. exec is a separate subresource kubectl exec does not operate directly on the pods resource. It calls the pods/exec subresource: ...

A green Ready status and a correct node configuration are not the same guarantee. Consider several node classes with configuration baselines in Git. The baselines define resource reservations, eviction thresholds, and image garbage collection settings. Actual host files can differ from those baselines while Kubernetes continues reporting the nodes as ready. This scenario lets us examine the problem without describing a particular cluster or operations tool. A node can work now yet react differently from its peers once memory or disk becomes scarce. ...

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.