Change username.
This commit is contained in:
@@ -35,7 +35,7 @@ Follow these steps to build and provision the entire cluster from scratch.
|
|||||||
|
|
||||||
### Step 1: Customize Configuration (Optional)
|
### 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`**:
|
1. **`Vagrantfile`**:
|
||||||
* `USERNAME`: Change this if you want to create a different user on the VMs.
|
* `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**:
|
1. **SSH into the first control plane node**:
|
||||||
```bash
|
```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.
|
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.
|
||||||
|
Reference in New Issue
Block a user