Hello everyone I have trouble with k3s on PC with Ubuntu I w rancher-users #random

Title

able-oil-52301

07/25/2022, 6:20 PM

Hello everyone. I have trouble with k3s (on PC with Ubuntu). I was using k3d and decided to switch to k3s. After installing k3s i get this error when using kubectl:

error: yaml: line 9: mapping values are not allowed in this context

I tried to stop (k3s-killall.sh) and uninstall (k3s-uninstall.sh) and delete directories:

/etc/rancher
/var/lib/rancher
~/.kube

I probably forgot something else because new installation:

curl -sfL <https://get.k3s.io> | sh -

ends with same result. Can any of you give me some advice?

white-battery-15789

07/26/2022, 2:18 PM

you can try disable some stuff

ls /var/lib/rancher/k3s/server/manifests
ccm.yaml      local-storage.yaml  rolebindings.yaml  traefik.yaml.skip
coredns.yaml  traefik.yaml

you can flag --disable traefik https://rancher.com/docs/k3s/latest/en/installation/disable-flags/

--disable value                            (components) Do not deploy packaged components and delete any deployed components (valid items: coredns, servicelb, traefik, local-storage, metrics-server)

https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/

im not using k3s for a while but i think default traefik is 1.7, i guess its probably due soma syntax change on kubernetes component. since it uses traefik 1.7 it should be the issue. you can try disable one by one of this components until find the issue

able-oil-52301

07/26/2022, 4:36 PM

Thank you for your response. I installed k3s v1.24.3+k3s1 (with embedded Traefik v2.6.2). Today I tried connect k3s server from another PC (in same VPN network) and I get nice result:

mm@archer:~$ kubectl get node -o wide
NAME     STATUS   ROLES                  AGE   VERSION        INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
cellar   Ready    control-plane,master   19h   v1.24.3+k3s1   192.168.0.8   <none>        Ubuntu 20.04.4 LTS   5.4.0-122-generic   <containerd://1.6.6-k3s1>

but from same PC, where is k3s server installed still:

#(any kubectl command)
error: yaml: line 9: mapping values are not allowed in this context

From this, I conclude that the k3s server is completely fine and the problem will be in the client side that queries the server. (i don't use kubectl symlink k3s)

white-battery-15789

07/26/2022, 4:48 PM

ah i see

so installation went ok, you may check kubectl version you should also check, kubeconfig file, and compare them

able-oil-52301

07/26/2022, 4:54 PM

It is magic for me. I copied kubeconfig from server to another PC a it works (kubectl requested k3s server and I get good results). On server...with same kubeconfig...just nothing...only error message

white-battery-15789

07/26/2022, 6:27 PM

did you chekc kubectl version?

might be that

https://austinsnerdythings.com/2021/08/30/how-to-create-a-proxmox-ubuntu-cloud-init-image/

able-oil-52301

07/26/2022, 6:31 PM

david@sklep:~$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
error: unable to parse the server version: invalid character '<' looking for beginning of value

white-battery-15789

07/26/2022, 6:35 PM

sorry i send the link on wrong thread. how about the working kubectl?

might be it

different kubectl version

able-oil-52301

07/26/2022, 6:39 PM

It seems to be OK. I copied

/etc/rancher/k3s/k3s.yaml

~/.kube/config

Thank you for your help.

sorry

4 Views

#random Join Slack