kubesec vs kube-linter: what each one catches, and how to read them in CI
Both scan Kubernetes YAML before it reaches the cluster, differently. One manifest through both, the score traps (a pass that exits 2), and the fixes.
Pipelines, builds and Helm releases: shipping changes without breaking production.
6 postsRSS feed
Both scan Kubernetes YAML before it reaches the cluster, differently. One manifest through both, the score traps (a pass that exits 2), and the fixes.
A metadata-only ALTER TABLE waits for its lock behind one long transaction, and every query queues behind it. See the queue, cancel it, use lock_timeout.
ansible-vault encrypts the file, not the output. How debug, verbose results and diffs leak a secret into CI logs, what no_log hides, and the cleanup order.
A dev plan that renames prod resources is reading prod's state. Read the plan, find the backend key, and re-init with -reconfigure, not -migrate-state.
sensitive = true only hides values in plan output. How a prod password reaches a CI log, how to confirm it without printing it, and how to rotate it.
"Error acquiring the state lock" or "state blob is already locked": read Lock Info, prove the holder is dead, run terraform force-unlock ID, then clean up.