<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure on Build. Run. Repeat.</title><link>https://buildrunrepeat.com/tags/azure/</link><description>Recent content in Azure on Build. Run. Repeat.</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 01 Jan 2023 09:00:00 -0400</lastBuildDate><atom:link href="https://buildrunrepeat.com/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing your vCenter server certificate? TKG needs to know about it…</title><link>https://buildrunrepeat.com/posts/replacing-your-vcenter-server-certificate-tkg-needs-to-know-about-it/</link><pubDate>Sun, 01 Jan 2023 09:00:00 -0400</pubDate><guid>https://buildrunrepeat.com/posts/replacing-your-vcenter-server-certificate-tkg-needs-to-know-about-it/</guid><description>&lt;p&gt;I recently ran into an issue where TKGm had suddenly failed to connect to the vCenter server.&lt;/p&gt;
&lt;p&gt;The issue turned out to be TLS-related, and I noticed that the vCenter server certificate had been replaced&amp;hellip;&lt;/p&gt;
&lt;p&gt;Due to the certificate issue, Cluster API components failed to communicate with vSphere, causing cluster reconciliation to fail, among other vSphere-related operations.&lt;/p&gt;
&lt;p&gt;Since all TKG clusters in the environment were deployed with the &lt;code&gt;VSPHERE_TLS_THUMBPRINT&lt;/code&gt; parameter specified, replacing the vCenter certificate breaks the connection to vSphere, as the TLS thumbprint changes as well.&lt;/p&gt;</description></item></channel></rss>