-
Notifications
You must be signed in to change notification settings - Fork 3.7k
CFP: parse VXLAN headers into Hubble flows #28001
Copy link
Copy link
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/hubbleImpacts hubble server or relayImpacts hubble server or relayarea/monitorImpacts monitoring, access logging, flow logging, visibility of datapath traffic.Impacts monitoring, access logging, flow logging, visibility of datapath traffic.kind/cfpCilium Feature ProposalCilium Feature Proposalkind/featureThis introduces new functionality.This introduces new functionality.
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/hubbleImpacts hubble server or relayImpacts hubble server or relayarea/monitorImpacts monitoring, access logging, flow logging, visibility of datapath traffic.Impacts monitoring, access logging, flow logging, visibility of datapath traffic.kind/cfpCilium Feature ProposalCilium Feature Proposalkind/featureThis introduces new functionality.This introduces new functionality.
Cilium Feature Proposal
Describe the feature you'd like
VXLAN is used in the context of egress gateway (possibly in other contexts as well but I'm not aware of that). If Hubble included some info from VXLAN headers into a flow, we would be able to distinguish between egress gateway traffic and other VXLAN traffic.
(Optional) Describe your proposed solution
I don't think Cilium currently emits VXLAN packets today. If it doesn't, then the initial step to take is to add VXLAN headers to monitor events. The next step is to implement a VXLAN header parser in Hubble. At a minimum, we probably want to extract the VNI and the outer IP header.