<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nkp on Anish Bista</title><link>https://anishbista.org/tags/nkp/</link><description>Recent content in Nkp on Anish Bista</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 17:38:23 +0000</lastBuildDate><atom:link href="https://anishbista.org/tags/nkp/index.xml" rel="self" type="application/rss+xml"/><item><title>The Case of the Phantom Webhook Timeout: How a Floating IP blocked entire Nutanix Kubernetes Platform Deployment</title><link>https://anishbista.org/blog/the-case-of-the-phantom-webhook-timeout-how-a-floating-ip-blocked-entire-nutanix-kubernetes/</link><pubDate>Fri, 10 Jul 2026 17:38:23 +0000</pubDate><guid>https://anishbista.org/blog/the-case-of-the-phantom-webhook-timeout-how-a-floating-ip-blocked-entire-nutanix-kubernetes/</guid><description>&lt;p>While bootstrapping a Nutanix Kubernetes Platform (NKP) 2.18 management cluster on AHV, the entire deployment ground to a halt at the very first component install. nkp create capi-components never got past cert-manager and because everything downstream (cluster-api-operator, and the rest of the cluster bootstrap) depends on that step, the whole cluster build was blocked.&lt;/p>
&lt;p>The error itself gave almost no clue as to why:&lt;/p>
&lt;pre tabindex="0">&lt;code>Post &amp;#34;https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s&amp;#34;:
 context deadline exceeded (Client.Timeout exceeded while awaiting headers)
&lt;/code>&lt;/pre>&lt;p>This kept repeating for 30+ minutes straight in the kube-apiserver logs, not a one-off startup race, but a persistent failure. The cert-manager Helm release sat stuck in pending-install. Reinstalling it manually made pods look healthy for a moment, but the next webhook-dependent step failed identically. Something below the application layer was broken.&lt;/p></description></item></channel></rss>