<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tkgs on Build. Run. Repeat.</title><link>https://buildrunrepeat.com/tags/tkgs/</link><description>Recent content in Tkgs on Build. Run. Repeat.</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 May 2024 09:00:00 -0400</lastBuildDate><atom:link href="https://buildrunrepeat.com/tags/tkgs/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing Missing TKRs in Existing TKGS Deployments</title><link>https://buildrunrepeat.com/posts/fixing-missing-tkrs-in-existing-tkgs-deployment/</link><pubDate>Wed, 01 May 2024 09:00:00 -0400</pubDate><guid>https://buildrunrepeat.com/posts/fixing-missing-tkrs-in-existing-tkgs-deployment/</guid><description>&lt;p&gt;I regularly check the &lt;a href="https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-releases/services/rn/vmware-tanzu-kubernetes-releases-release-notes/index.html"&gt;Tanzu Kubernetes Releases (TKR) release notes page&lt;/a&gt; for new updates.
Yesterday, a new TKR was released with support for Kubernetes 1.28.8, and while attempting to test this new version in my TKGS environment, I realized that the TKR was not present in my environment and I started wondering why, as normally, when new TKRs are released, they immediately become available for deployment, since the vCenter is subscribed to the VMware public content library where all the TKRs are hosted. This time, that was not the case, so I started investigating.&lt;/p&gt;</description></item></channel></rss>