<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OnCallReady blog</title><link>https://oncallready.dev/blog/</link><atom:link href="https://oncallready.dev/blog/rss.xml" rel="self" type="application/rss+xml"/><description>Real incidents and Linux / Kubernetes / SRE gotchas, explained.</description><language>en</language><lastBuildDate>Thu, 22 Oct 2026 08:00:00 GMT</lastBuildDate>
<item><title>Backstage catalog-info.yaml validation errors, and how to fix each one</title><link>https://oncallready.dev/blog/backstage-catalog-info-yaml-validation-errors/</link><guid isPermaLink="true">https://oncallready.dev/blog/backstage-catalog-info-yaml-validation-errors/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>Policy check failed, must have required property 'owner', missing or empty kind, Unknown field: what each Backstage catalog error means and how to fix it.</description><category>Platform engineering</category></item>
<item><title>bpftrace one-liners that answer real production questions</title><link>https://oncallready.dev/blog/bpftrace-one-liners-production/</link><guid isPermaLink="true">https://oncallready.dev/blog/bpftrace-one-liners-production/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>Eight bpftrace one-liners for who is busy, which open fails, what keeps starting, how big the reads are and where the CPU goes, with their real output.</description><category>Linux</category><category>Performance</category></item>
<item><title>CPU throttling: p99 latency doubled, but the box is 70% idle</title><link>https://oncallready.dev/blog/cpu-throttling-cfs-quota-p99-latency/</link><guid isPermaLink="true">https://oncallready.dev/blog/cpu-throttling-cfs-quota-p99-latency/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>A CPU limit below the service's peak shows up as tail latency, not as high CPU. Prove it with cpu.max and nr_throttled, then raise or drop the quota.</description><category>Linux</category><category>Performance</category><category>Kubernetes</category></item>
<item><title>Crossplane resource not Ready: debug the XR top-down with crossplane resource trace</title><link>https://oncallready.dev/blog/crossplane-composite-resource-not-ready/</link><guid isPermaLink="true">https://oncallready.dev/blog/crossplane-composite-resource-not-ready/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>An XR stuck at SYNCED False or READY False: trace the tree, read the first unhealthy object, then fix the Composition, the patch or the credentials.</description><category>Platform engineering</category><category>Kubernetes</category></item>
<item><title>Crossplane function-patch-and-transform: patches, transforms and the three traps</title><link>https://oncallready.dev/blog/crossplane-function-patch-and-transform/</link><guid isPermaLink="true">https://oncallready.dev/blog/crossplane-function-patch-and-transform/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>Patch and transform in a Crossplane v2 pipeline: patch types, map and string transforms, readinessChecks, and testing it all with composition render.</description><category>Platform engineering</category><category>Kubernetes</category></item>
<item><title>High iowait on Linux: which disk, which process, and how to calm it down</title><link>https://oncallready.dev/blog/high-iowait-iostat-x-pidstat-d/</link><guid isPermaLink="true">https://oncallready.dev/blog/high-iowait-iostat-x-pidstat-d/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>vmstat says wa 37%. Read iostat -x the right way (await and aqu-sz, not just %util), name the process with pidstat -d, then cap it with io.max.</description><category>Linux</category><category>Performance</category></item>
<item><title>Kafka consumer lag keeps growing: read the group, then find out why</title><link>https://oncallready.dev/blog/kafka-consumer-lag-growing/</link><guid isPermaLink="true">https://oncallready.dev/blog/kafka-consumer-lag-growing/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>Lag that only grows means the group is not committing. Read kafka-consumer-groups --describe and --state, spot a rebalance storm, and fix max.poll.records.</description><category>Kafka</category></item>
<item><title>Kafka NOT_ENOUGH_REPLICAS: &quot;Messages are rejected since there are fewer in-sync replicas than required&quot;</title><link>https://oncallready.dev/blog/kafka-not-enough-replicas-min-insync-replicas/</link><guid isPermaLink="true">https://oncallready.dev/blog/kafka-not-enough-replicas-min-insync-replicas/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>Producers with acks=all get NotEnoughReplicasException when the ISR is below min.insync.replicas. Find the missing brokers and fix them, not the setting.</description><category>Kafka</category></item>
<item><title>Reset Kafka consumer offsets to a date and time, safely</title><link>https://oncallready.dev/blog/kafka-reset-offsets-to-datetime/</link><guid isPermaLink="true">https://oncallready.dev/blog/kafka-reset-offsets-to-datetime/</guid><pubDate>Thu, 22 Oct 2026 08:00:00 GMT</pubDate><description>kafka-consumer-groups --reset-offsets --to-datetime: stop the group, mind the milliseconds and UTC, dry-run, export a backup, then execute, and undo it.</description><category>Kafka</category></item>
<item><title>The CKS exam in 2026: domains, weights and what the tasks look like</title><link>https://oncallready.dev/blog/cks-exam-2026-domains-and-tasks/</link><guid isPermaLink="true">https://oncallready.dev/blog/cks-exam-2026-domains-and-tasks/</guid><pubDate>Wed, 21 Oct 2026 08:00:00 GMT</pubDate><description>The Certified Kubernetes Security Specialist in 2026: format, the six domains and their weights, the exam environment, and a typical task for each domain.</description><category>Kubernetes</category><category>Security</category></item>
<item><title>Rotating the etcd encryption key without locking your Secrets: &quot;no matching key was found&quot;</title><link>https://oncallready.dev/blog/kubernetes-encryption-key-rotation-no-matching-key/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-encryption-key-rotation-no-matching-key/</guid><pubDate>Wed, 21 Oct 2026 08:00:00 GMT</pubDate><description>Every Secret read fails with InternalError after a key rotation: what the error means, how to get the old key back, and the rotation order that avoids it.</description><category>Kubernetes</category><category>Security</category><category>Secrets</category></item>
<item><title>kubesec vs kube-linter: what each one catches, and how to read them in CI</title><link>https://oncallready.dev/blog/kubesec-vs-kube-linter/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubesec-vs-kube-linter/</guid><pubDate>Wed, 21 Oct 2026 08:00:00 GMT</pubDate><description>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.</description><category>Kubernetes</category><category>Security</category><category>CI/CD</category></item>
<item><title>Kyverno 1.19: moving from ClusterPolicy to ValidatingPolicy and ImageValidatingPolicy</title><link>https://oncallready.dev/blog/kyverno-1-19-clusterpolicy-to-validatingpolicy/</link><guid isPermaLink="true">https://oncallready.dev/blog/kyverno-1-19-clusterpolicy-to-validatingpolicy/</guid><pubDate>Wed, 21 Oct 2026 08:00:00 GMT</pubDate><description>Kyverno 1.19 deprecates ClusterPolicy and plans to remove it in 1.20. How the CEL policy types map, one rule converted, and a rollout that breaks nothing.</description><category>Kubernetes</category><category>Security</category></item>
<item><title>curl: (60) &quot;unable to get local issuer certificate&quot;: the two causes</title><link>https://oncallready.dev/blog/curl-unable-to-get-local-issuer-certificate/</link><guid isPermaLink="true">https://oncallready.dev/blog/curl-unable-to-get-local-issuer-certificate/</guid><pubDate>Wed, 14 Oct 2026 08:00:00 GMT</pubDate><description>curl error 60: no chain to a trusted root. Either the server skips its intermediate or your box lacks the root. Tell which, then fix nginx, the OS or Java.</description><category>Networking</category><category>Linux</category><category>JVM</category></item>
<item><title>ALB 502 vs 503 vs 504 on AWS: what each one says about your targets</title><link>https://oncallready.dev/blog/aws-alb-502-503-504/</link><guid isPermaLink="true">https://oncallready.dev/blog/aws-alb-502-503-504/</guid><pubDate>Fri, 09 Oct 2026 08:00:00 GMT</pubDate><description>From an AWS ALB: 502 = the target refused or broke the connection, 503 = no target, 504 = no answer in time. Real outputs for each, and the fixes.</description><category>AWS</category><category>Networking</category><category>SRE</category></item>
<item><title>S3 AccessDenied explained: identity policy, bucket policy, KMS key or SCP?</title><link>https://oncallready.dev/blog/aws-s3-accessdenied-explained/</link><guid isPermaLink="true">https://oncallready.dev/blog/aws-s3-accessdenied-explained/</guid><pubDate>Fri, 09 Oct 2026 08:00:00 GMT</pubDate><description>The end of an AWS AccessDenied message names the policy type that said no. Five real S3 errors decoded, from a missing ListBucket to a KMS key and an SCP.</description><category>AWS</category><category>Secrets</category><category>SRE</category></item>
<item><title>EC2 instance can't reach the internet: route tables, NAT gateways and blackhole routes</title><link>https://oncallready.dev/blog/ec2-private-instance-no-internet-nat-gateway/</link><guid isPermaLink="true">https://oncallready.dev/blog/ec2-private-instance-no-internet-nat-gateway/</guid><pubDate>Fri, 09 Oct 2026 08:00:00 GMT</pubDate><description>apt update hangs, Session Manager says TargetNotConnected. Read the private route table, spot the blackhole, rebuild the NAT gateway in a public subnet.</description><category>AWS</category><category>Networking</category><category>Linux</category></item>
<item><title>PostgreSQL disk full: an inactive replication slot kept all the WAL</title><link>https://oncallready.dev/blog/postgresql-disk-full-inactive-replication-slot/</link><guid isPermaLink="true">https://oncallready.dev/blog/postgresql-disk-full-inactive-replication-slot/</guid><pubDate>Fri, 09 Oct 2026 08:00:00 GMT</pubDate><description>pg_wal filled the disk and PostgreSQL PANICked. Free space safely, find the slot that pins the WAL, drop it, and cap it with max_slot_wal_keep_size.</description><category>PostgreSQL</category><category>Filesystem</category><category>SRE</category></item>
<item><title>A 2-second migration took the site down: ALTER TABLE and the PostgreSQL lock queue</title><link>https://oncallready.dev/blog/postgresql-migration-lock-queue-alter-table/</link><guid isPermaLink="true">https://oncallready.dev/blog/postgresql-migration-lock-queue-alter-table/</guid><pubDate>Fri, 09 Oct 2026 08:00:00 GMT</pubDate><description>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.</description><category>PostgreSQL</category><category>SRE</category><category>CI/CD</category></item>
<item><title>PostgreSQL &quot;FATAL: sorry, too many clients already&quot;: count, cap, pool</title><link>https://oncallready.dev/blog/postgresql-sorry-too-many-clients-already/</link><guid isPermaLink="true">https://oncallready.dev/blog/postgresql-sorry-too-many-clients-already/</guid><pubDate>Fri, 09 Oct 2026 08:00:00 GMT</pubDate><description>max_connections is a budget that every pod's pool spends. How to get in when it is gone, find who took it, stop the bleeding without a restart, and pool.</description><category>PostgreSQL</category><category>Kubernetes</category><category>SRE</category></item>
<item><title>Ansible reports &quot;changed&quot; on every run and restarts the service: changed_when and handlers</title><link>https://oncallready.dev/blog/ansible-changed-every-run-restarts-service/</link><guid isPermaLink="true">https://oncallready.dev/blog/ansible-changed-every-run-restarts-service/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>A playbook that changes nothing says changed=3 and restarts nginx every run. Why command and shell always report changed, how handlers fire, and the fix.</description><category>Ansible</category><category>Linux</category><category>SRE</category></item>
<item><title>Ansible printed the password in the job log: no_log, ansible-vault and rotating the secret</title><link>https://oncallready.dev/blog/ansible-secret-leaked-job-log-no-log/</link><guid isPermaLink="true">https://oncallready.dev/blog/ansible-secret-leaked-job-log-no-log/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>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.</description><category>Ansible</category><category>Secrets</category><category>CI/CD</category></item>
<item><title>Ansible &quot;UNREACHABLE!&quot; and &quot;Missing sudo password&quot;: what each error means and how to fix it</title><link>https://oncallready.dev/blog/ansible-unreachable-missing-sudo-password/</link><guid isPermaLink="true">https://oncallready.dev/blog/ansible-unreachable-missing-sudo-password/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>UNREACHABLE means Ansible never got an SSH session; Missing sudo password means it got in and become failed. Six real causes, their exact errors and fixes.</description><category>Ansible</category><category>Linux</category><category>Networking</category></item>
<item><title>cert-manager certificate stuck: Ready False, a pending Order and an HTTP-01 challenge that gets 404</title><link>https://oncallready.dev/blog/cert-manager-certificate-stuck-pending-http01/</link><guid isPermaLink="true">https://oncallready.dev/blog/cert-manager-certificate-stuck-pending-http01/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>The Certificate never becomes Ready and the issuer says it is fine. Follow CertificateRequest, Order and Challenge to the HTTP-01 self-check that fails.</description><category>Kubernetes</category><category>Networking</category></item>
<item><title>HTTPRoute not working: Accepted False, NotAllowedByListeners and RefNotPermitted</title><link>https://oncallready.dev/blog/gateway-api-httproute-not-accepted/</link><guid isPermaLink="true">https://oncallready.dev/blog/gateway-api-httproute-not-accepted/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>You applied an HTTPRoute, the Gateway returns 404 and kubectl get looks fine. The answer is in the route's status conditions: read each reason, fix it.</description><category>Kubernetes</category><category>Networking</category></item>
<item><title>How to run an incident as incident commander: roles, severity, cadence and handoff</title><link>https://oncallready.dev/blog/how-to-run-an-incident-as-incident-commander/</link><guid isPermaLink="true">https://oncallready.dev/blog/how-to-run-an-incident-as-incident-commander/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>An incident commander does not debug. A SEV2 from four people changing production at once to a clean handoff, and what the IC says at each step.</description><category>SRE</category></item>
<item><title>How to write an incident status update: impact, action, next update time</title><link>https://oncallready.dev/blog/incident-status-update-template/</link><guid isPermaLink="true">https://oncallready.dev/blog/incident-status-update-template/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>Who is affected and how, what you are doing, and when the next update comes - with templates for customers, executives and support.</description><category>SRE</category></item>
<item><title>Istio 503s explained: Envoy response flags UH, UF, NR, URX and friends</title><link>https://oncallready.dev/blog/istio-503-envoy-response-flags-uh-uf-nr-urx/</link><guid isPermaLink="true">https://oncallready.dev/blog/istio-503-envoy-response-flags-uh-uf-nr-urx/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>Every request through an Istio sidecar is logged with a flag saying who failed and why. How to read UH, UF, URX, NR, NC and UT, and the command for each.</description><category>Kubernetes</category><category>Networking</category><category>Observability</category></item>
<item><title>&quot;Vault is sealed&quot; after a restart: unseal keys, the threshold and auto-unseal</title><link>https://oncallready.dev/blog/vault-is-sealed-after-restart-unseal/</link><guid isPermaLink="true">https://oncallready.dev/blog/vault-is-sealed-after-restart-unseal/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>After a reboot every app that needs a secret fails with 503 Vault is sealed. Why Vault restarts sealed, how to unseal with key shares, and auto-unseal.</description><category>Secrets</category><category>SRE</category><category>Linux</category></item>
<item><title>Vault &quot;permission denied&quot; with the right policy: KV v2 and the data/ path</title><link>https://oncallready.dev/blog/vault-permission-denied-kv-v2-data-path/</link><guid isPermaLink="true">https://oncallready.dev/blog/vault-permission-denied-kv-v2-data-path/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>The policy says kv/reports/* and the token still gets a 403. KV v2 reads at kv/data/ and lists at kv/metadata/: read the URL, test the token, fix it.</description><category>Secrets</category><category>SRE</category></item>
<item><title>Vault token expired at 3 a.m.: TTL, max TTL, renewal and Vault Agent</title><link>https://oncallready.dev/blog/vault-token-expired-max-ttl-vault-agent/</link><guid isPermaLink="true">https://oncallready.dev/blog/vault-token-expired-max-ttl-vault-agent/</guid><pubDate>Thu, 08 Oct 2026 08:00:00 GMT</pubDate><description>The app renewed its Vault token and still died at 3 a.m.: renewal stops at the max TTL and the leases die with it. How to read it, and the Vault Agent fix.</description><category>Secrets</category><category>SRE</category><category>Linux</category></item>
<item><title>Argo CD app OutOfSync right after a sync: mutating webhooks, controllers and ignoreDifferences</title><link>https://oncallready.dev/blog/argocd-outofsync-ignoredifferences/</link><guid isPermaLink="true">https://oncallready.dev/blog/argocd-outofsync-ignoredifferences/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>Synced, then OutOfSync again seconds later - something rewrites a field git declares. Find it with argocd app diff, then fix git or ignore narrowly.</description><category>GitOps</category><category>Kubernetes</category></item>
<item><title>I deleted a 40 GB log and df didn't change. Where did the space go?</title><link>https://oncallready.dev/blog/deleted-log-df-not-freed/</link><guid isPermaLink="true">https://oncallready.dev/blog/deleted-log-df-not-freed/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>rm removes a name, not the data. Why df and du disagree after deleting an open file, how lsof +L1 finds it, and how to get the space back without a reboot.</description><category>Linux</category><category>Filesystem</category></item>
<item><title>DNS resolution failed for every service: resolv.conf, systemd-resolved, CoreDNS</title><link>https://oncallready.dev/blog/dns-resolution-failed-systemd-resolved/</link><guid isPermaLink="true">https://oncallready.dev/blog/dns-resolution-failed-systemd-resolved/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>When every app fails name lookups at the same minute, one shared resolver is down. Find it with resolv.conf, getent vs dig, and one query per hop.</description><category>Networking</category><category>Linux</category><category>Kubernetes</category><category>SRE</category></item>
<item><title>Docker container keeps restarting: exit codes, restart policies, docker logs</title><link>https://oncallready.dev/blog/docker-container-restarting-exit-code/</link><guid isPermaLink="true">https://oncallready.dev/blog/docker-container-restarting-exit-code/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>A container stuck in Restarting (1) is a crash loop. Read the exit code, the restart count and each attempt's logs, then fix the startup, not the policy.</description><category>Docker</category><category>Linux</category><category>SRE</category></item>
<item><title>Docker host out of disk but docker system df looks fine</title><link>https://oncallready.dev/blog/docker-no-space-left-on-device/</link><guid isPermaLink="true">https://oncallready.dev/blog/docker-no-space-left-on-device/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>A full Docker host is usually container logs, which docker system df does not count. Find the space with df and du, prune safely, and set log rotation.</description><category>Docker</category><category>Linux</category><category>Filesystem</category><category>SRE</category></item>
<item><title>Exit code 137, OOMKilled, and the JVM that fits its heap but not its container</title><link>https://oncallready.dev/blog/exit-code-137-oomkilled-jvm/</link><guid isPermaLink="true">https://oncallready.dev/blog/exit-code-137-oomkilled-jvm/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>137 = 128 + SIGKILL. How to tell a cgroup OOM kill from a host OOM, why -Xmx equal to the memory limit gets your Java pod killed, and how to size it.</description><category>Memory</category><category>Kubernetes</category><category>JVM</category></item>
<item><title>Load average 15 on 4 cores, but the CPU is 90% idle</title><link>https://oncallready.dev/blog/high-load-idle-cpu-d-state/</link><guid isPermaLink="true">https://oncallready.dev/blog/high-load-idle-cpu-d-state/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>Linux load average counts processes waiting on disk or NFS, not just CPU. Spot D-state processes, why kill -9 cannot touch them, and what to fix instead.</description><category>Linux</category><category>Processes</category></item>
<item><title>kubectl: x509: certificate has expired or is not yet valid (renewing kubeadm certificates)</title><link>https://oncallready.dev/blog/kubeadm-x509-certificate-has-expired/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubeadm-x509-certificate-has-expired/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>A kubeadm cluster a year old and never upgraded stops answering kubectl. Check expiry, renew, restart the static pods, refresh your kubeconfig.</description><category>Kubernetes</category></item>
<item><title>Node NotReady: kubelet stuck in activating (auto-restart) because swap is on</title><link>https://oncallready.dev/blog/kubelet-swap-node-notready/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubelet-swap-node-notready/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>The kubelet refuses to run with swap on. Read it from systemctl and journalctl, why swapoff alone comes back after a reboot, and the full fix.</description><category>Kubernetes</category><category>systemd</category><category>Linux</category></item>
<item><title>CrashLoopBackOff: how to find out why the pod keeps restarting</title><link>https://oncallready.dev/blog/kubernetes-crashloopbackoff-debug/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-crashloopbackoff-debug/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>CrashLoopBackOff is a symptom, not a cause. Read Last State and the exit code, get the previous container's logs, check probes and events: a checklist.</description><category>Kubernetes</category><category>SRE</category></item>
<item><title>CreateContainerConfigError: couldn't find key in ConfigMap (and other missing config)</title><link>https://oncallready.dev/blog/kubernetes-createcontainerconfigerror-missing-configmap-key/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-createcontainerconfigerror-missing-configmap-key/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>New pods stuck in CreateContainerConfigError or ContainerCreating after a config cleanup? Read the Events, find the missing ConfigMap or key, fix it.</description><category>Kubernetes</category></item>
<item><title>What happens between kubectl delete pod and the container disappearing</title><link>https://oncallready.dev/blog/kubernetes-pod-deletion-sigterm-grace-sigkill/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-pod-deletion-sigterm-grace-sigkill/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>SIGTERM, the grace period, SIGKILL - and endpoint removal at the same time. Why pods drop requests on deploy, and how preStop and graceful shutdown fix it.</description><category>Kubernetes</category><category>Processes</category></item>
<item><title>Pod stuck in Pending: how to read FailedScheduling (requests, taints, affinity, PVCs)</title><link>https://oncallready.dev/blog/kubernetes-pod-pending-failedscheduling/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-pod-pending-failedscheduling/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>&quot;0/3 nodes are available&quot; is a per-node tally. Decode each reason - Insufficient cpu, untolerated taint, node affinity, unbound PVC - and fix that one.</description><category>Kubernetes</category></item>
<item><title>PVC stuck in Terminating: the pvc-protection finalizer and what still uses it</title><link>https://oncallready.dev/blog/kubernetes-pvc-stuck-terminating-finalizer/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-pvc-stuck-terminating-finalizer/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>A deleted PVC that stays Terminating is protected, not broken. Find the pod that still mounts it, and why removing the finalizer is the wrong fix.</description><category>Kubernetes</category></item>
<item><title>Downtime on every Kubernetes deploy: Recreate, readiness probes and the preStop race</title><link>https://oncallready.dev/blog/kubernetes-rolling-update-downtime-readiness-prestop/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-rolling-update-downtime-readiness-prestop/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>20-40 seconds of 503s on every rollout of a two-second app. Check the strategy, then readiness, then shutdown - and prove zero downtime with one rollout.</description><category>Kubernetes</category><category>SRE</category></item>
<item><title>Kubernetes Service not working: pods Running, zero restarts, no traffic</title><link>https://oncallready.dev/blog/kubernetes-service-no-endpoints-selector/</link><guid isPermaLink="true">https://oncallready.dev/blog/kubernetes-service-no-endpoints-selector/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>Healthy pods, a Service, and Connection refused. Check the selector (empty endpoints), readiness (ready false) and targetPort - in that order.</description><category>Kubernetes</category><category>Networking</category></item>
<item><title>nginx 502 Bad Gateway but the API is up: reading error.log</title><link>https://oncallready.dev/blog/nginx-502-bad-gateway-upstream/</link><guid isPermaLink="true">https://oncallready.dev/blog/nginx-502-bad-gateway-upstream/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>&quot;502 Bad Gateway&quot; over nginx/1.26.3 (Ubuntu) means nginx could not reach your app. Read error.log, tell refused from timed out, and fix the right link.</description><category>Networking</category><category>Linux</category><category>Docker</category><category>SRE</category></item>
<item><title>&quot;No space left on device&quot; but df shows free space: the 3 causes, in the order to check</title><link>https://oncallready.dev/blog/no-space-left-df-shows-free/</link><guid isPermaLink="true">https://oncallready.dev/blog/no-space-left-df-shows-free/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>ENOSPC with a half-empty disk: check inodes (df -i), then deleted-but-open files (lsof +L1), then ext4 reserved blocks (tune2fs) - and how to fix each.</description><category>Linux</category><category>Filesystem</category></item>
<item><title>OpenShift &quot;Application is not available&quot;: the 503 and its three causes</title><link>https://oncallready.dev/blog/openshift-application-is-not-available-503/</link><guid isPermaLink="true">https://oncallready.dev/blog/openshift-application-is-not-available-503/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>The grey router page means no pod got the request: wrong host or path, no ready endpoints, or a Route on the wrong port. The oc commands that tell which.</description><category>OpenShift</category><category>Kubernetes</category><category>Networking</category></item>
<item><title>p99 latency is 25 seconds and the error rate is zero: histograms, histogram_quantile and timeouts</title><link>https://oncallready.dev/blog/prometheus-p99-latency-histogram-quantile/</link><guid isPermaLink="true">https://oncallready.dev/blog/prometheus-p99-latency-histogram-quantile/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>Slow requests that end in 200 are successes, and abandoned ones are never counted. How to read p99 from Prometheus buckets and find the wait behind it.</description><category>Observability</category><category>JVM</category><category>SRE</category></item>
<item><title>Why set -e doesn't catch a failure in foo | bar (and the other gaps)</title><link>https://oncallready.dev/blog/set-e-does-not-catch-pipe/</link><guid isPermaLink="true">https://oncallready.dev/blog/set-e-does-not-catch-pipe/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>set -euo pipefail is the right header, but it has holes - pipelines, conditions, &amp;&amp; chains and local x=$(cmd). What each one misses and how to close it.</description><category>Bash</category><category>Linux</category></item>
<item><title>systemd: your StartLimitIntervalSec is in the wrong section (and silently ignored)</title><link>https://oncallready.dev/blog/systemd-startlimitintervalsec-ignored/</link><guid isPermaLink="true">https://oncallready.dev/blog/systemd-startlimitintervalsec-ignored/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>In [Service], systemd ignores StartLimitIntervalSec: &quot;Unknown key name ... ignoring.&quot; It belongs in [Unit]. How to spot it, and the default limit.</description><category>systemd</category><category>Linux</category></item>
<item><title>Terraform count vs for_each: removing one item destroys the rest of the list</title><link>https://oncallready.dev/blog/terraform-count-index-shift-destroy/</link><guid isPermaLink="true">https://oncallready.dev/blog/terraform-count-index-shift-destroy/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>Removing one item from a count list re-indexes everything after it, so Terraform replaces them. Switch to for_each and move state with moved blocks.</description><category>Terraform</category><category>Azure</category><category>SRE</category></item>
<item><title>Terraform plan in dev wants to replace production: wrong state, backend key or workspace</title><link>https://oncallready.dev/blog/terraform-plan-replace-production-wrong-state/</link><guid isPermaLink="true">https://oncallready.dev/blog/terraform-plan-replace-production-wrong-state/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>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.</description><category>Terraform</category><category>Azure</category><category>CI/CD</category><category>SRE</category></item>
<item><title>Terraform secret leaked in a CI log: sensitive = true, TF_LOG and rotating first</title><link>https://oncallready.dev/blog/terraform-secret-leaked-in-ci-log/</link><guid isPermaLink="true">https://oncallready.dev/blog/terraform-secret-leaked-in-ci-log/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>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.</description><category>Terraform</category><category>CI/CD</category><category>Azure</category><category>SRE</category></item>
<item><title>Terraform &quot;Error acquiring the state lock&quot;: when force-unlock is safe</title><link>https://oncallready.dev/blog/terraform-state-lock-force-unlock/</link><guid isPermaLink="true">https://oncallready.dev/blog/terraform-state-lock-force-unlock/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>&quot;Error acquiring the state lock&quot; or &quot;state blob is already locked&quot;: read Lock Info, prove the holder is dead, run terraform force-unlock ID, then clean up.</description><category>Terraform</category><category>Azure</category><category>CI/CD</category><category>SRE</category></item>
<item><title>Zombie processes (&lt;defunct&gt;): why kill doesn't work and what does</title><link>https://oncallready.dev/blog/zombie-processes-defunct/</link><guid isPermaLink="true">https://oncallready.dev/blog/zombie-processes-defunct/</guid><pubDate>Sat, 03 Oct 2026 08:00:00 GMT</pubDate><description>A zombie is a child that exited but was never reaped. Why kill -9 does nothing, how to find the parent, and why containers need a PID 1 that reaps.</description><category>Processes</category><category>Linux</category><category>Docker</category></item>
</channel></rss>
