Hi, I am trying to set up rke2 with cilium on Rocky 9 as foundation for my homelab.

# rke/config.yaml
selinux: true
write-kubeconfig-mode: "0644"
debug: true
cni:
  - cilium
tls-san:
- lab.home

Cilium config:

# rke2/server/manifests/rke2-cilium-config.yaml
apiVersion: <http://helm.cattle.io/v1|helm.cattle.io/v1>
kind: HelmChartConfig
metadata:
  name: rke2-cilium
  namespace: kube-system
spec:
  valuesContent: |-
    eni:
      enabled: true

I then run

curl -sfL <https://get.rke2.io> | sh -

and start the server with

systemctl enable rke2-server.service

and systemctl enable

rke2-server.service

However, one of the cilium operator pods hangs in pending state:

NAME                                                    READY   STATUS      RESTARTS        AGE
cilium-jj6v9                                            1/1     Running     0               2m55s
cilium-operator-97b9d9bc6-dszwf                         0/1     Pending     0               2m55s
cilium-operator-97b9d9bc6-wzch5                         1/1     Running     0               2m55s
cloud-controller-manager-lab.home                       1/1     Running     1 (3m17s ago)   3m18s
etcd-lab.home                                           1/1     Running     0               3m16s
helm-install-rke2-cilium-46r72                          0/1     Completed   0               3m6s
helm-install-rke2-coredns-7rcxs                         0/1     Completed   0               3m6s
helm-install-rke2-ingress-nginx-lg2sx                   0/1     Completed   0               3m6s
helm-install-rke2-metrics-server-96654                  0/1     Completed   0               3m5s
helm-install-rke2-snapshot-controller-crd-zm2b5         0/1     Completed   0               3m4s
helm-install-rke2-snapshot-controller-rpzn7             0/1     Completed   2               3m4s
helm-install-rke2-snapshot-validation-webhook-9gc6d     0/1     Completed   0               3m3s
kube-apiserver-lab.home                                 1/1     Running     0               3m21s
kube-controller-manager-lab.home                        1/1     Running     0               3m20s
kube-proxy-lab.home                                     1/1     Running     0               3m3s
kube-scheduler-lab.home                                 1/1     Running     0               3m20s
rke2-coredns-rke2-coredns-565dfc7d75-vv5zh              1/1     Running     0               2m55s
rke2-coredns-rke2-coredns-autoscaler-6c48c95bf9-fm6dg   1/1     Running     0               2m55s
rke2-ingress-nginx-controller-kg4b2                     1/1     Running     0               2m4s
rke2-metrics-server-c9c78bd66-4zjsm                     1/1     Running     0               2m17s
rke2-snapshot-controller-6f7bbb497d-5hk78               1/1     Running     0               2m4s
rke2-snapshot-validation-webhook-65b5675d5c-fzw9p       1/1     Running     0               2m17s

When I kubectl describe the pod, I get the following output:

Warning  FailedScheduling  3m2s (x2 over 3m12s)  default-scheduler  0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports..

I am out of ideas on how I could debug this any further... My server runs at IP 10.0.0.244 if that is important.