for the checking of things I think we should consider kubectl exec -ti -n kube-system ds/cilium -- cilium status tho this doesn't show tunnel mode maybe consider custom columns instead of jq. kubectl get nodes -o custom-columns=name:.metadata.name,node-ip:.status.addresses[].address,pod-cidr:.spec.podCIDRs[]
2/15/2023⬢ Cilium Routing Options There are a variety of routing options in Cilium: By default cilium will deploy in an overlay mode and encapsulate all traffic between nodes. We also support Direct Routing. Where we route all traffic between nodes directly using the underlying network In this lab, we will explore what happens to packets that are transmitted between pods when using the Direct Routing option. We don't know that the nodes are part of 10.0.0.0/8 in fact docker exec -ti clab-bgp-cplane-demo-control-plane ip addr shows that they are part of a /24
2/7/2023Link https://hackmd.io/@mauilion/cilium-ipv6 Youtube link https://www.youtube.com/watch?v=IgPqIi67hSA Summary: Setup an cluster and deploy cilium in routed mode. Show connectivity between pods and then use tcpdump to show identity labels encoded in the flow label header for ipv6 traffic. Setup. We will use a kind cluster for this learn more about kind here
12/17/2022Summary of changes. With this release we are deploying a new configmap into the cilium namespace. The name of this configmap is cilium-ee-olm-overrides. The purpose is two fold. the default configmap looks like this: apiVersion: v1 data: RELATED_IMAGE_CERTGEN: quay.io/cilium/certgen:v0.1.5@sha256:0c2b71bb3469990e7990e7e26243617aa344b5a69a4ce465740b8577f9d48ab9@sha256:0c2b71bb3469990e7990e7e26243617aa344b5a69a4ce465740b8577f9d48ab9
9/15/2022