https://www.hrbac.cz/tags/rancher/ Recent content in rancher on David Hrbáč Hugo -- gohugo.io en-us Wed, 26 Aug 2026 12:00:00 +0000 https://www.hrbac.cz/2026/08/rancher-migrating-server-url-to-a-new-domain-with-split-horizon-dns/ Wed, 26 Aug 2026 12:00:00 +0000 https://www.hrbac.cz/2026/08/rancher-migrating-server-url-to-a-new-domain-with-split-horizon-dns/ I recently migrated a Rancher installation from an old domain name to a new one. The setup was slightly more interesting than a simple DNS rename because Rancher was used from different network locations and the environment used split-horizon DNS. The simplified topology looked like this: local downstream clusters -> internal RR DNS -> Rancher ingress -> internal/self-signed CA remote downstream clusters -> public DNS -> F5 VIP -> public CA certificate users -> public DNS -> F5 VIP -> public CA certificate As an ASCII diagram: https://www.hrbac.cz/2026/08/rancher-waiting-for-plan-to-be-applied-and-empty-connection-info/ Tue, 25 Aug 2026 21:51:43 +0000 https://www.hrbac.cz/2026/08/rancher-waiting-for-plan-to-be-applied-and-empty-connection-info/ 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.