This message was deleted.
# rke2
a
This message was deleted.
b
looks like I will just install/fix it up via the cli from a mgmt workstation with the right .kube/config is the best approach.
maybe not. rogue@TUMBLER:~/ciliumLBPool$ k get nodes NAME STATUS ROLES AGE VERSION kusanagi-pool1-78a45fe2-b4j2c Ready control-plane,etcd,master,worker 12h v1.25.10+rke2r1 kusanagi-pool1-78a45fe2-p9mnr Ready control-plane,etcd,master,worker 12h v1.25.10+rke2r1 kusanagi-pool1-78a45fe2-v6l2j Ready control-plane,etcd,master,worker 12h v1.25.10+rke2r1 rogue@TUMBLER:~/ciliumLBPool$ cilium status /¯¯\ /¯¯\__/¯¯\ Cilium: OK \__/¯¯\__/ Operator: OK /¯¯\__/¯¯\ Envoy DaemonSet: disabled (using embedded mode) \__/¯¯\__/ Hubble Relay: disabled \__/ ClusterMesh: disabled DaemonSet cilium Desired: 3, Ready: 3/3, Available: 3/3 Deployment cilium-operator Desired: 2, Ready: 2/2, Available: 2/2 Containers: cilium-operator Running: 2 cilium Running: 3 Cluster Pods: 20/20 managed by Cilium Helm chart version: Image versions cilium rancher/mirrored-cilium-ciliumv1.13.2 3 cilium-operator rancher/mirrored-cilium-operator-genericv1.13.2 2 rogue@TUMBLER:~/ciliumLBPool$ cilium hubble enable Error: Unable to enable Hubble: release: not found
a
Hubble is enabled via HelmConfig
b
I figured it out via destroying all resources and reinstalling via cilium install but if I want to play around with replacing metallb with cilium's l2 load balancing I have to dig deeper in replacing kubeProxy....so following https://devopstales.github.io/kubernetes/rke2-cilium/ to get some hints for node creation.
ya... seems helm is the best approach. Yuck, not a fan of helm but this is to play around so don't need a perfect gitops repo to deploy it. If needed, I can do some argo magic with kustomize.
218 Views