socket termination reconciler not triggered when kpr=true #40028
Description
Is there an existing issue for this?
- I have searched the existing issues
Version
equal or higher than v1.17.4 and lower than v1.18.0
What happened?
A bug happened!
Under KPR=true in main branch, the reconciler for socket termination is not triggered. Noticed while working on a fix for #39470 .
https://github.com/cilium/cilium/blob/main/pkg/loadbalancer/reconciler/termination.go#L104
if !(p.ExtConfig.EnableSocketLB || p.ExtConfig.BPFSocketLBHostnsOnly) {
return nil
}
We bail out and return nil here.
Temporary workaround is to use --bpf-lb-sock=true in addition to KPR=true until it is fixed.
Metadata
Metadata
Assignees
Labels
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.Anything related to our kube-proxy replacement.This is a bug in the Cilium logic.This was reported by a user in the Cilium community, eg via Slack.This functionality worked fine before, but was broken in a newer release of Cilium.This issue requires triaging to establish severity and next steps.This issue will prevent the release of the next version of Cilium.
Type
Projects
Status