This message was deleted.
# k3s
a
This message was deleted.
c
have you looked at the logs to see why they’re crashing?
e
Copy code
➜ kubectl -n kube-system logs local-path-provisioner-957fdf8bc-8k64c
time="2023-08-15T16:29:51Z" level=fatal msg="Error starting daemon: invalid empty flag helper-pod-file and it also does not exist at ConfigMap kube-system/local-path-config with err: Get \"<https://10.43.0.1:443/api/v1/namespaces/kube-system/configmaps/local-path-config>\": dial tcp 10.43.0.1:443: i/o timeout"
Copy code
➜ kubectl -n kube-system logs metrics-server-648b5df564-wlr7f                                      
Error: unable to load configmap based request-header-client-ca-file: Get "<https://10.43.0.1:443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication>": dial tcp 10.43.0.1:443: i/o timeout
looks like the API isn't happy?
c
do you have a local firewall enabled that’s blocking communication with the apiserver?
ufw/firewalld/etc?
e
I have iptables but it looks like k3s injected all the rules?
plus default policy on all chains is accept
a
I encountered the same problem
bash Copy code
curl –sfL \
     https://rancher-mirror.oss-cn-beijing.aliyuncs.com/k3s/k3s-install.sh | \
     INSTALL_K3S_MIRROR=cn sh -s - \
     --node-external-ip=xxxxx \
     --advertise-address=xxxxx \
     --system-default-registry "registry.cn-hangzhou.aliyuncs.com" \
     --write-kubeconfig ~/.kube/config \
     --write-kubeconfig-mode 644 \
     --disable traefik
remove --node-external-ip=xxxxx --advertise-address=xxxxx and there will be no problem.
420 Views