What would you like to be added:
Add a way to tell ebpf the kubelete probe src ip address, so that in xdp and sockops, we donot need to process these connection/packet.
And then no need to even send metric info/authz req to kmesh-daemon.
I did some research the kubelet probe src ip commonly is node ip or pod sub net gateway address, diff because cni implement.
For calico env, the src ip is node ip 172.18.0.5
For kindnet, the src ip is 192.168.1.1
apiVersion: v1
kind: Node
metadata:
annotations:
labels:
beta.kubernetes.io/arch: amd64
beta.kubernetes.io/os: linux
kubernetes.io/arch: amd64
kubernetes.io/hostname: kind-worker
kubernetes.io/os: linux
name: kind-worker
resourceVersion: "21264"
uid: c0a23c49-52f2-4e8e-8480-79fa88208001
spec:
podCIDR: 192.168.1.0/24
podCIDRs:
- 192.168.1.0/24
providerID: kind://docker/kind/kind-worker
status:
addresses:
- address: 172.18.0.5
type: InternalIP
- address: kind-worker
type: Hostname
What would you like to be added:
Add a way to tell ebpf the kubelete probe src ip address, so that in xdp and sockops, we donot need to process these connection/packet.
And then no need to even send metric info/authz req to kmesh-daemon.
I did some research the kubelet probe src ip commonly is node ip or pod sub net gateway address, diff because cni implement.
For calico env, the src ip is node ip 172.18.0.5
For kindnet, the src ip is 192.168.1.1