From b3990e3a4d1acf6d82993eaa0611ffc6c5f364e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A5l-Kristian=20Hamre?= Date: Tue, 12 Aug 2025 23:31:25 +0200 Subject: [PATCH] Change username. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ae5c8cd..942f3d5 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ Follow these steps to build and provision the entire cluster from scratch. ### Step 1: Customize Configuration (Optional) -The project is configured to work out-of-the-box for user `pkhamre`. If your setup is different, you may need to adjust the following files: +The project is configured to work out-of-the-box for user `kube`. If your setup is different, you may need to adjust the following files: 1. **`Vagrantfile`**: * `USERNAME`: Change this if you want to create a different user on the VMs. @@ -70,7 +70,7 @@ After the playbook completes, you can access the cluster and verify its status. 1. **SSH into the first control plane node**: ```bash - ssh pkhamre@192.168.122.101 + ssh kube@192.168.122.101 ``` 2. **Check the node status**: The `kubectl` command-line tool is pre-configured for your user. All three control plane nodes should have the `control-plane` role.