From 95ec073b9b9d2af7ebdd6ca7d8b6aa5df27bac7a Mon Sep 17 00:00:00 2001
From: Marco van Zijl <marco@mvzijl.nl>
Date: Sat, 3 May 2025 21:15:48 +0200
Subject: [PATCH] Update README to correct Talos client configuration endpoint
 instructions

---
 readme.md | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/readme.md b/readme.md
index 0c85ef1..a38b598 100644
--- a/readme.md
+++ b/readme.md
@@ -62,6 +62,18 @@ talosctl gen config             \
 talosctl config merge ./talosconfig
 ```
 
+Then correct the endpoint in the Talos client configuration:
+
+```yaml
+# ~/.talos/config
+context: veda
+contexts:
+    veda:
+        endpoints: 
+            - 192.168.0.1
+# (...)
+```
+
 For controlplane nodes:
 
 ```bash
@@ -97,18 +109,6 @@ talosctl gen config \
         $API_ENDPOINT
 ```
 
-Then change the endpoint in the Talos client configuration:
-
-```yaml
-# ~/.talos/config
-context: veda
-contexts:
-    veda:
-        endpoints: 
-            - 192.168.0.1
-# (...)
-```
-
 ### Bootstrapping
 
 Apply the configuration to each node:
@@ -118,9 +118,10 @@ talosctl apply-config --insecure --file rendered/master1.yaml  --nodes 192.168.0
 ```
 
 Optionally, check the status.
+Point the Talos API endpoint directly to the node, since etcd, and thereby kube-vip, is not up.
 
 ```bash
-talosctl -n 192.168.0.10 dashboard
+talosctl -n 192.168.0.10 -e 192.168.0.10 dashboard
 ```
 
 To start the cluster, we need to bootstrap the etcd cluster.