From fe8d31090680d8ff1214b42e008710f1c49e9589 Mon Sep 17 00:00:00 2001 From: David Zisky Date: Wed, 18 Dec 2019 15:35:19 +0100 Subject: [PATCH] Updated info about using kubeconfig K3S no longer puts "localhost" in kubeconfig but "127.0.0.1" instead. Therefore - updated instructions. --- content/k3s/latest/en/configuration/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/configuration/_index.md b/content/k3s/latest/en/configuration/_index.md index 1f3cc7d7bf8..7ee0ae25a13 100644 --- a/content/k3s/latest/en/configuration/_index.md +++ b/content/k3s/latest/en/configuration/_index.md @@ -90,7 +90,7 @@ Accessing Cluster from Outside ----------------------------- Copy `/etc/rancher/k3s/k3s.yaml` on your machine located outside the cluster as `~/.kube/config`. Then replace -"localhost" with the IP or name of your K3s server. `kubectl` can now manage your K3s cluster. +"127.0.0.1" with the IP or name of your K3s server. `kubectl` can now manage your K3s cluster. Node Registration -----------------