The latest articles on DEV Community by mikailh (@mikailh). https://dev.to/mikailh https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4015636%2F8d39f53d-e8d5-44ab-b228-9dec48e0aada.png https://dev.to/mikailh en mikailh Sun, 05 Jul 2026 00:17:12 +0000 https://dev.to/mikailh/kubeadm-init-fails-with-the-number-of-available-cpus-1-is-less-than-the-required-2-on-an-azure-3k69 https://dev.to/mikailh/kubeadm-init-fails-with-the-number-of-available-cpus-1-is-less-than-the-required-2-on-an-azure-3k69 <p>While setting up a self-managed Kubernetes cluster on Azure VMs, I hit this error when running <code>sudo kubeadm init</code> on a Standard_B1s VM (1 vCPU / 1 GB RAM):</p> <p>[ERROR NumCPU]: the number of available CPUs 1 is less than the required 2</p> <p>After checking Stack Overflow and the official Kubernetes documentation ("Before you begin"), I confirmed that kubeadm requires at least 2 CPUs to install the control plane.</p> <p>The fix: I stopped the VM and resized it from Standard_B1s to Standard_B2s (2 vCPU / 4 GB RAM) from the Azure portal, then ran <code>kubeadm init</code> again — the preflight checks passed and the control plane initialized successfully.</p> <p>Posting this in case it helps someone hitting the same issue on a low-tier cloud VM. Thanks to the community for the answers that pointed me in the right direction!</p> kubernetes azure devops