Skip to content

Checks for conflicting packet mark bits to validate interoperability #17109

Closed
@aditighag

Description

Cilium uses a set of bits in the skb mark field to store metadata. However, these bits can conflict with other systems filtering packets based on selective bits (e.g., Kubernetes). Conflicts can lead to packet drops, but these drops can be indeterministic based on whether the set bits by cilium overlap with the bits used for filtering packets.

We should add preliminary checks to warn users about such scenarios. These checks can be part of the agent bootstrap (agent already iterates over some of the cilium-specific rules), or they can be added to a conformance test that validates the underlying system state when cilium is being installed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementThis would improve or streamline existing functionality.sig/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions