-
Notifications
You must be signed in to change notification settings - Fork 3.8k
L4 policies stay in bpf map after policy change #2270
Copy link
Copy link
Closed
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.priority/highThis is considered vital to an upcoming release.This is considered vital to an upcoming release.
Metadata
Metadata
Assignees
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.priority/highThis is considered vital to an upcoming release.This is considered vital to an upcoming release.
General Information
How to reproduce the issue
docker run -d --name "app1" --net cilium-net -l "id=app1" cilium/demo-httpdcilium policy import l3l4.jsondocker run --rm -ti --net cilium-net -l "id=app2" cilium/demo-client curl 'http://app1/public'cilium policy delete --allcilium policy import l3.jsondocker run --rm -ti --net cilium-net -l "id=app2" cilium/demo-client curl 'http://app1/public'cilium bpf policy get <choose app1 epid>The IDs are different, but we can see that the old policy entry which filtered on specific L4 ports is still available, even though we deleted the cilium policy.
Final policy: