<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OhSudo — new Kubernetes articles</title><description>New Kubernetes articles from OhSudo: practical fixes for DevOps engineers, SysAdmins and IT folks.</description><link>https://ohsudo.com/</link><language>en-us</language><atom:link href="https://ohsudo.com/rss/kubernetes.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes &quot;Forbidden: User cannot list resource&quot;: give exactly the rights it needs with RBAC</title><link>https://ohsudo.com/articles/kubernetes-forbidden-user-cannot-list-resource/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-forbidden-user-cannot-list-resource/</guid><description>Fix Kubernetes &quot;Forbidden: User cannot list resource&quot;: read who and what is missing, test with kubectl auth can-i, then add a Role and RoleBinding.</description><pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>rbac</category><category>kubectl</category><category>service-accounts</category><category>permissions</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>kubectl &quot;x509: certificate signed by unknown authority&quot;: your kubeconfig doesn&apos;t trust this cluster</title><link>https://ohsudo.com/articles/kubectl-x509-certificate-signed-by-unknown-authority/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubectl-x509-certificate-signed-by-unknown-authority/</guid><description>Fix kubectl &quot;x509: certificate signed by unknown authority&quot;: get a fresh kubeconfig for a recreated cluster, compare the CA, and handle proxies that inspect TLS.</description><pubDate>Fri, 13 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>kubeconfig</category><category>tls</category><category>x509</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Kubernetes CreateContainerConfigError: a missing Secret or ConfigMap, and how to find it</title><link>https://ohsudo.com/articles/kubernetes-createcontainerconfigerror/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-createcontainerconfigerror/</guid><description>Fix Kubernetes CreateContainerConfigError: kubectl describe names the missing Secret, ConfigMap or key. Check the namespace and the key, then let the pod restart.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>secrets</category><category>configmap</category><category>pods</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Kubernetes pods &quot;Evicted&quot;: find the pressure on the node, and stop it from coming back</title><link>https://ohsudo.com/articles/kubernetes-pods-evicted-diskpressure/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-pods-evicted-diskpressure/</guid><description>Fix Kubernetes pods with status Evicted: read why with describe, handle DiskPressure and MemoryPressure on the node, clean up, set requests and limits, delete old pods.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>evicted</category><category>diskpressure</category><category>resources</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>kubectl &quot;The connection to the server localhost:8080 was refused&quot;: your kubeconfig is missing</title><link>https://ohsudo.com/articles/kubectl-connection-to-server-localhost-8080-refused/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubectl-connection-to-server-localhost-8080-refused/</guid><description>Fix kubectl &quot;The connection to the server localhost:8080 was refused&quot;: kubectl has no kubeconfig. Set it up for kubeadm, k3s, minikube, EKS, GKE or AKS, and under sudo.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>kubeconfig</category><category>k3s</category><category>kubeadm</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Kubernetes &quot;container has runAsNonRoot and image will run as root&quot;: fix the image or the pod</title><link>https://ohsudo.com/articles/kubernetes-container-has-runasnonroot-and-image-will-run-as-root/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-container-has-runasnonroot-and-image-will-run-as-root/</guid><description>CreateContainerConfigError with runAsNonRoot: the image runs as root or has a non-numeric USER. Fix the Dockerfile, set runAsUser, and keep restricted security.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>security</category><category>securitycontext</category><category>docker</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Kubernetes ImagePullBackOff and ErrImagePull: find out why the image won’t pull</title><link>https://ohsudo.com/articles/kubernetes-imagepullbackoff/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-imagepullbackoff/</guid><description>Fix ImagePullBackOff: read the pull error in kubectl describe, then fix the image name or tag, registry credentials, Docker Hub rate limits, network or architecture.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>images</category><category>registry</category><category>imagepullsecrets</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Kubernetes pod stuck in Pending: &quot;0/3 nodes are available: Insufficient cpu&quot;</title><link>https://ohsudo.com/articles/kubernetes-pod-pending-insufficient-cpu/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-pod-pending-insufficient-cpu/</guid><description>Fix pods stuck in Pending: read the FailedScheduling event, then fix CPU and memory requests, taints, node selectors, volumes or the cluster size.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>scheduling</category><category>resources</category><category>requests</category><category>taints</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Kubernetes CrashLoopBackOff: 7 causes and how to find yours</title><link>https://ohsudo.com/articles/kubernetes-crashloopbackoff/</link><guid isPermaLink="true">https://ohsudo.com/articles/kubernetes-crashloopbackoff/</guid><description>CrashLoopBackOff means the container keeps exiting. Read the exit code and the previous logs, then fix the crash, OOM kill, probe or command.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate><category>Kubernetes</category><category>kubernetes</category><category>kubectl</category><category>pods</category><category>crashloopbackoff</category><category>probes</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item></channel></rss>