From 7ffcf5b932cc4064e5680efb20bf6fe6e7179cd4 Mon Sep 17 00:00:00 2001 From: SpiReCZ Date: Tue, 19 Nov 2024 23:35:03 +0000 Subject: [PATCH] docs: update getting started Add missing talosconfig parameter. Signed-off-by: SpiReCZ Signed-off-by: Andrey Smirnov --- website/content/v1.6/introduction/getting-started.md | 8 +++++--- website/content/v1.7/introduction/getting-started.md | 8 +++++--- website/content/v1.8/introduction/getting-started.md | 8 +++++--- website/content/v1.9/introduction/getting-started.md | 8 +++++--- 4 files changed, 20 insertions(+), 12 deletions(-) diff --git a/website/content/v1.6/introduction/getting-started.md b/website/content/v1.6/introduction/getting-started.md index 0548aaaaa..d74938cc9 100644 --- a/website/content/v1.6/introduction/getting-started.md +++ b/website/content/v1.6/introduction/getting-started.md @@ -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: diff --git a/website/content/v1.7/introduction/getting-started.md b/website/content/v1.7/introduction/getting-started.md index ff4220be3..5d3062a20 100644 --- a/website/content/v1.7/introduction/getting-started.md +++ b/website/content/v1.7/introduction/getting-started.md @@ -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: diff --git a/website/content/v1.8/introduction/getting-started.md b/website/content/v1.8/introduction/getting-started.md index c36247e81..2decf49ba 100644 --- a/website/content/v1.8/introduction/getting-started.md +++ b/website/content/v1.8/introduction/getting-started.md @@ -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: diff --git a/website/content/v1.9/introduction/getting-started.md b/website/content/v1.9/introduction/getting-started.md index c36247e81..2decf49ba 100644 --- a/website/content/v1.9/introduction/getting-started.md +++ b/website/content/v1.9/introduction/getting-started.md @@ -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: