Hey! I'm currently trying to use Cilium alongside K3s. I'm currently using Cilium 1.11.6 and K3s v1.24.2+k3s2 (also tried v1.23.8+k3s2). However, I am receiving this error:

kubectl logs -n kube-system cilium-4vt6k 
Defaulted container "cilium-agent" out of: cilium-agent, mount-cgroup (init), clean-cilium-state (init)
Error from server: Get "<https://192.168.1.3:10250/containerLogs/kube-system/cilium-4vt6k/cilium-agent>": proxy error from 192.168.1.3:6443 while dialing 192.168.1.3:10250, code 500: 500 Internal Server Error

K3s config:

advertise-address: {{ private_ip }}
bind-address: {{ private_ip }}
node-ip: {{ private_ip }}

node-external-ip: {{ hostvars[inventory_hostname]['ansible_default_ipv4']['address'] }}

kubelet-arg:
  - address={{ private_ip }}

kube-apiserver-arg:
  - kubelet-preferred-address-types=InternalIP

flannel-backend: none
disable-kube-proxy: true
disable-network-policy: true
disable:
  - servicelb
  - traefik
  - local-storage

Cilium config:

k8sServiceHost: {{ hostvars[groups['server'][0]]['private_ip'] }}
k8sServicePort: 6443
kubeProxyReplacement: strict

bandwidthManager: true

externalIPs:
  enabled: true

hostPort:
  enabled: true

nodePort:
  enabled: true

hostServices:
  enabled: true

hubble:
  enabled: false

nodeinit:
  restartPods: true

Do you have logs from the server node?

I believe I found a solution for this: https://github.com/k3s-io/k3s/issues/5857

yeah, that shouldn’t be necessary though. If you have debug-level logs for the server node when this happens, I’m curious to know why it’s failing.