Martynas Pumputis
Martynas Pumputis
Mainly to catch possible discrepancies between different verifier versions.
A user on Fedora 28 reported that kubelet is not able to locate the `weave-net` CNI bin. The relevant params of the kubelet: `--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/usr/libexec/cni` set by kubeadm v1.10.1...
From time to time, in kernel logs we see: ``` [ 2717.970445] IPv4: martian source 10.32.0.5 from 10.32.0.2, on dev datapath [ 2717.970446] ll header: 00000000: ff ff ff ff...
When installing with `cilium install`, the cilium-cli could detect whether K8s' kube-proxy is present in a cluster. If not, then it could install Cilium with `--set kubeProxyReplacement=strict`.
As seen in https://github.com/cilium/cilium/pull/21337, the `status.PodIP` might be not set. In the testing code we have a few places in which we rely on that field: ``` > git grep...
To stress tests the new infrastructure even more until we have more tests in the conformance suite. The CI passed: https://github.com/cilium/cilium/actions/runs/3096983007/jobs/5013158158
Could be another workaround for the problem described in https://github.com/cilium/cilium/pull/18113.
Once https://github.com/cilium/ebpf/pull/716 has been merged, we can start using the multi-link kprobes. This should significantly reduce the startup time.