Kyr Shatskyy 4388ffb703 Make a note about KUBECONFIG environment variable. ...

A new to k3s user might get "surprised" by error messages from kubectl
or k3s like:

  WARN[0000] Unable to read /etc/rancher/k3s/k3s.yaml, please start server with --write-kubeconfig-mode to modify kube config permissions
  error: error loading config file "/etc/rancher/k3s/k3s.yaml": open /etc/rancher/k3s/k3s.yaml: permission denied

It can happen when there is a k3s installed on the same machine and
`/etc/rancher/k3s/k3s.yaml` present.

Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>

2023-03-17 23:35:30 +01:00

..

aws.md

Capitalize Terraform

2023-01-23 13:10:20 -08:00

azure.md

Capitalize Terraform

2023-01-23 13:10:20 -08:00

digitalocean.md

Capitalize Terraform

2023-01-23 13:10:20 -08:00

equinix-metal.md

Remove unsupported front matter fields

2022-09-23 10:11:24 -07:00

gcp.md

Capitalize Terraform

2023-01-23 13:10:20 -08:00

helm-cli.md

Make a note about KUBECONFIG environment variable.

2023-03-17 23:35:30 +01:00

hetzner-cloud.md

Capitalize Terraform

2023-01-23 13:10:20 -08:00

outscale-qs.md

Capitalize Terraform

2023-01-23 13:10:20 -08:00

prime.md

Update Prime description per feedback

2023-01-12 09:28:08 -08:00

vagrant.md

Remove unsupported front matter fields

2022-09-23 10:11:24 -07:00