adamant-kite-43734
08/16/2022, 11:40 AMadamant-kite-43734
08/16/2022, 4:40 PMbrainy-postman-1566
08/16/2022, 11:35 PMadamant-kite-43734
08/17/2022, 8:59 AMadamant-kite-43734
08/18/2022, 3:04 AMred-waitress-37932
08/18/2022, 4:19 PMadamant-kite-43734
08/19/2022, 7:59 AMred-musician-8168
08/19/2022, 8:27 PMadamant-kite-43734
08/19/2022, 10:00 PMadamant-kite-43734
08/19/2022, 6:21 PMfaint-airport-39912
08/20/2022, 7:29 AMcurl -sfL <https://get.k3s.io> | sh -s - server --datastore-endpoint='<postgres://k3s:password@192.168.1013:5432/k3s>' --token='K102xxxxx''
I'm using to add new master node, but it is giving me following error so can you someone look into it and help ??
FYI, This highly available k3s cluster is configured one year back. `
systemd[1]: k3s.service: Service hold-off time over, scheduling restart.
systemd[1]: k3s.service: Scheduled restart job, restart counter is at 97783.
systemd[1]: Stopped Lightweight Kubernetes.
systemd[1]: Starting Lightweight Kubernetes...
sh[23500]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
sh[23500]: /bin/sh: 1: /usr/bin/systemctl: not found
k3s[23512]: time="2022-08-11T07:19:00Z" level=info msg="Starting k3s v1.24.3+k3s1 (990ba0e8)"
k3s[23512]: time="2022-08-11T07:19:00Z" level=info msg="Configuring postgres database connection pooling: maxIdleConns=2, maxOpenConns=
k3s[23512]: time="2022-08-11T07:19:00Z" level=info msg="Configuring database table schema and indexes, this may take a moment..."
k3s[23512]: time="2022-08-11T07:19:00Z" level=info msg="Database tables and indexes are up to date"
k3s[23512]: time="2022-08-11T07:19:00Z" level=info msg="Kine available at <unix://kine.sock>"
k3s[23512]: time="2022-08-11T07:19:00Z" level=fatal msg="starting kubernetes: preparing server:
bootstrap data already found and encryp
"
systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: k3s.service: Failed with result 'exit-code'.
`adamant-kite-43734
08/20/2022, 8:22 PMadamant-kite-43734
08/20/2022, 9:46 PMadamant-kite-43734
08/21/2022, 6:10 PMadamant-kite-43734
08/22/2022, 7:18 AMadamant-kite-43734
08/23/2022, 4:27 AMadamant-kite-43734
08/23/2022, 12:41 PMadamant-kite-43734
08/25/2022, 4:47 AMrefined-toddler-64572
08/25/2022, 8:02 PM1.24.3+k3s1
) on Ubuntu 22.04.1 with ZFS (2.1.4
) and external containerd (1.5.9
). Works GREAT, no day-to-day issues. What I've been struggling with is when K3s uses an external containerd -- either kubelet / cadvisor is a bit wonky with metrics in that the image=
and container=
are missing which breaks many dashboards. I can't tell if this is a K3s / kubelet issue, cadvisor issue, containerd issue.. not sure where to seek advise. Kube-Prometheus-Stack is deployed, works well as long as a dashboard doesn't try to use something like container_cpu_usage_seconds_total{image!=""}
returns an empty set as the image reference is missing, but that does return data when K3s uses bundled containerd. Suggestions welcomed.adamant-kite-43734
08/25/2022, 8:50 PMadamant-kite-43734
08/26/2022, 1:11 AMflat-fish-63205
08/26/2022, 12:26 PMwhile true; do kubectl exec -it <pod_name> /bin/ls; done
Running above command will give intermittent error:
Error from server: error dialing backend: EOF
clever-air-65544
08/26/2022, 3:46 PMadamant-kite-43734
08/26/2022, 4:45 PMprehistoric-diamond-4224
08/27/2022, 11:14 AM*v1beta1.Ingress
which was deprecated in 1.22.
Is there a traefik v1 version that i can upgrade to that supports v1.Ingress
?
I'd rather not update traefik to v2 since i'd have to migrate all of our ingresses, many of which are rmanaged by helm charts.
Would nginx be compatibe with standard Ingress resources? Is a migration from traefiik v1.81 to nginx ingress feasible without modifying existing ingress resources?
Thank youadamant-kite-43734
08/29/2022, 3:17 AMadamant-kite-43734
08/29/2022, 4:31 PMgifted-morning-94496
08/29/2022, 4:54 PMmicroscopic-smartphone-81961
08/29/2022, 5:57 PMadamant-kite-43734
08/30/2022, 3:02 AM