When I first build the minimal kernel config, I think I only tested it by running the end-to-end tests which for, net-next CI job, run with KPR=strict. Thus, kube-proxy was probably not, or barely, tested.
This commits adds a few kernel configs that are currently causing errors for kube-proxy in the development VM.
pchaigno
commented
1 year ago
When I first build the minimal kernel config, I think I only tested it by running the end-to-end tests which for, net-next CI job, run with KPR=strict. Thus, kube-proxy was probably not, or barely, tested.
This commits adds a few kernel configs that are currently causing errors for kube-proxy in the development VM.
Reported-by: Maxim Mikityanskiy maxim@isovalent.com Signed-off-by: Paul Chaignon paul@cilium.io