mirror of
https://github.com/siderolabs/talos.git
synced 2025-12-05 17:41:34 +01:00
docs: fix typo
Fix sendi/receive. Signed-off-by: Till Hoffmann <till@thetillhoff.de> Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
This commit is contained in:
parent
f35b213b2b
commit
7a817df1cc
@ -308,7 +308,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
|
||||
talosctl --talosconfig talosconfig kubeconfig .
|
||||
```
|
||||
|
||||
The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
You can now watch as your cluster bootstraps, by using
|
||||
|
||||
```bash
|
||||
|
||||
@ -308,7 +308,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
|
||||
talosctl --talosconfig talosconfig kubeconfig .
|
||||
```
|
||||
|
||||
The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
You can now watch as your cluster bootstraps, by using
|
||||
|
||||
```bash
|
||||
|
||||
@ -308,7 +308,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
|
||||
talosctl --talosconfig talosconfig kubeconfig .
|
||||
```
|
||||
|
||||
The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
You can now watch as your cluster bootstraps, by using
|
||||
|
||||
```bash
|
||||
|
||||
@ -317,7 +317,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
|
||||
talosctl --talosconfig talosconfig kubeconfig .
|
||||
```
|
||||
|
||||
The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
You can now watch as your cluster bootstraps, by using
|
||||
|
||||
```bash
|
||||
|
||||
@ -317,7 +317,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
|
||||
talosctl --talosconfig talosconfig kubeconfig .
|
||||
```
|
||||
|
||||
The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
|
||||
You can now watch as your cluster bootstraps, by using
|
||||
|
||||
```bash
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user