This message was deleted.

Have you considered using rke2 instead? It uses most of k3s code and gives you more options, e.g. CNI plugin. For example, we have tests integrating rke2 + cilium-eBPF, more docs, more experience working with customers and users, etc, i.e. it'd be easier to provide you help

I believe the only options available through Civo are K3s and Talos. That said, after some further reading and testing, I think I may have figured out the bit I was missing. It looks like to use Cilium's gateway API, kube-proxy will need to be disabled and Cilium needs to manage instead. So I guess from here we'll need to confirm if we can access the nodes directly to update the K3s config to disable network policy and kube-proxy. I've poked around some with a privileged debug container, but I don't know that restarting the K3s service through a container is a smart idea. Or if we'd need to set these options in the control plane as well.