-
Notifications
You must be signed in to change notification settings - Fork 3.8k
L4 protocol policy needs to have always port #2292
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.area/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.priority/lowThis is considered nice to have.This is considered nice to have.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
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.area/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.priority/lowThis is considered nice to have.This is considered nice to have.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Hi,
I figured this week that if you have a policy that only allows TCP, it didn't work. You need to specify always the port too.
Example pod manifest:
https://raw.githubusercontent.com/cilium/cilium/master/examples/minikube/demo.yaml
Example policy:
CNP Describe: