DevOps Stack Exchange is a question and answer site for software engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure. It only takes a minute to sign up.
Sign up to join this community
When I run commands under k3s kubectl, I get
$ k3s kubectl version
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
How should I resolve this? Should I change the permissions of /etc/rancher/k3s/k3s.yaml
/etc/rancher/k3s/k3s.yamlFirst set up your an environmental variable for KUBECONFIG=~/.kube/config.
export KUBECONFIG=~/.kube/config
Then let's generate the file at that location. Your k3s.yaml file should NOT be world readable.. This is by-design. It should be owned by root and set to 0600. Instead copy the config locally as described here,
mkdir ~/.kube 2> /dev/null
sudo k3s kubectl config view --raw > "$KUBECONFIG"
chmod 600 "$KUBECONFIG"
You can add KUBECONFIG=~/.kube/config to your ~/.profile or ~/.bashrc to make it persist on reboot.
/usr/local/bin/ in front of "k3s". Which would make that line as this: sudo /usr/local/bin/k3s kubectl config view --raw > "$KUBECONFIG"
Aug 1, 2022 at 7:30
/usr/local/bin is not in your $PATH which would be pretty awkward anyway.
Aug 1, 2022 at 15:34
$PATH but it might be considered common practice and not mentioned because of that. I'm no linux expert of any kind, just commented in case someone like me encounters the same issue.
Aug 2, 2022 at 5:06
echo $PATH you should see /usr/local/bin in your path. Almost certainly CentOS does that. (also, CentOS is dead, everyone went to Rocky).
Aug 2, 2022 at 14:47
export PATH=$PATH:/usr/local/bin line to $HOME/.bashrc. (Just checked out Rocky Linux from wiki, might try that next time - thanks for the heads up)
Aug 3, 2022 at 4:49