This message was deleted.
# k3sa
adamant-kite-43734
06/04/2025, 5:40 PMThis message was deleted.
c
creamy-pencil-82913
06/04/2025, 5:52 PMYou disabled kube-proxy and then you're getting an error accessing the apiserver in-cluster endpoint because kube-proxy isn't running to set up iptables rules to handle traffic to it.
creamy-pencil-82913
06/04/2025, 5:53 PMWhy did you disable kube-proxy? If you're trying to use the Cilium kube-proxy replacement you need to do that at deployment time, as a prerequisite for Cilium CNI to function.
r
ripe-musician-92943
06/04/2025, 6:04 PMAh... that is plenty obvious. But I don't see how I can install Cilium at deployment time. At least there appear to be no mentions on how to do that in the docs. Looking at the blog posts I found dealing with this, I cannot find a mention of that either. (e.g. https://blog.stonegarden.dev/articles/2024/02/bootstrapping-k3s-with-cilium/)
ripe-musician-92943
06/04/2025, 6:23 PMThank you very much for the hint. I was missing the parameters
k8sServiceHostk8sServicePort12 Views