docs: update getting started

Add missing talosconfig parameter.

Signed-off-by: SpiReCZ <SpiReCZ@users.noreply.github.com>
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
This commit is contained in:
SpiReCZ 2024-11-19 23:35:03 +00:00 committed by Andrey Smirnov
parent c4c1a0d7c7
commit 7ffcf5b932
No known key found for this signature in database
GPG Key ID: FE042E3D4085A811
4 changed files with 20 additions and 12 deletions

View File

@ -279,7 +279,8 @@ At this point, Talos will form an `etcd` cluster, and start the Kubernetes contr
After a few moments, you will be able to download your Kubernetes client configuration and get started:
```sh
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
Running this command will add (merge) you new cluster into your local Kubernetes configuration.
@ -287,13 +288,14 @@ Running this command will add (merge) you new cluster into your local Kubernetes
If you would prefer the configuration to *not* be merged into your default Kubernetes configuration file, pass in a filename:
```sh
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
You should now be able to connect to Kubernetes and see your nodes:
```sh
kubectl get nodes
kubectl get nodes
```
And use talosctl to explore your cluster:

View File

@ -281,7 +281,8 @@ At this point, Talos will form an `etcd` cluster, and start the Kubernetes contr
After a few moments, you will be able to download your Kubernetes client configuration and get started:
```sh
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
Running this command will add (merge) you new cluster into your local Kubernetes configuration.
@ -289,13 +290,14 @@ Running this command will add (merge) you new cluster into your local Kubernetes
If you would prefer the configuration to _not_ be merged into your default Kubernetes configuration file, pass in a filename:
```sh
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
You should now be able to connect to Kubernetes and see your nodes:
```sh
kubectl get nodes
kubectl get nodes
```
And use talosctl to explore your cluster:

View File

@ -288,7 +288,8 @@ At this point, Talos will form an `etcd` cluster, and start the Kubernetes contr
After a few moments, you will be able to download your Kubernetes client configuration and get started:
```sh
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
Running this command will add (merge) you new cluster into your local Kubernetes configuration.
@ -296,13 +297,14 @@ Running this command will add (merge) you new cluster into your local Kubernetes
If you would prefer the configuration to _not_ be merged into your default Kubernetes configuration file, pass in a filename:
```sh
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
You should now be able to connect to Kubernetes and see your nodes:
```sh
kubectl get nodes
kubectl get nodes
```
And use talosctl to explore your cluster:

View File

@ -288,7 +288,8 @@ At this point, Talos will form an `etcd` cluster, and start the Kubernetes contr
After a few moments, you will be able to download your Kubernetes client configuration and get started:
```sh
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
Running this command will add (merge) you new cluster into your local Kubernetes configuration.
@ -296,13 +297,14 @@ Running this command will add (merge) you new cluster into your local Kubernetes
If you would prefer the configuration to _not_ be merged into your default Kubernetes configuration file, pass in a filename:
```sh
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2
talosctl kubeconfig alternative-kubeconfig --nodes 192.168.0.2 --endpoints 192.168.0.2 \
--talosconfig=./talosconfig
```
You should now be able to connect to Kubernetes and see your nodes:
```sh
kubectl get nodes
kubectl get nodes
```
And use talosctl to explore your cluster: