<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>rke2 on David Hrbáč</title>
    <link>https://www.hrbac.cz/tags/rke2/</link>
    <description>Recent content in rke2 on David Hrbáč</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 25 Aug 2026 21:51:43 +0000</lastBuildDate><atom:link href="https://www.hrbac.cz/tags/rke2/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rancher: Waiting for plan to be applied and empty connection info</title>
      <link>https://www.hrbac.cz/2026/08/rancher-waiting-for-plan-to-be-applied-and-empty-connection-info/</link>
      <pubDate>Tue, 25 Aug 2026 21:51:43 +0000</pubDate>
      
      <guid>https://www.hrbac.cz/2026/08/rancher-waiting-for-plan-to-be-applied-and-empty-connection-info/</guid>
      
      <description>I have recently hit an interesting Rancher provisioning issue after working on downstream RKE2 clusters managed by Rancher and backed by VMware vSphere.
The visible symptom was not very specific. Rancher UI kept showing the cluster in Reconciling state and reported that it was Waiting for plan to be applied. A new worker VM was created in vSphere, but provisioning did not really move forward. At first glance it looked like a new node provisioning problem, but the actual blocker was an older node in the cluster.</description>
      
    </item>
    
  </channel>
</rss>
