Skip to content

CFP: Move hubble v1.Events drop emitter to beta #33975

@joestringer

Description

@joestringer

Cilium v1.16 introduced support to forward drop events towards the kube-apiserver through v1.Events in order to provide better visibility into cluster networking behaviour to users (CFP, PR). The feature is enabled through Helm via hubble.dropEventEmitter or through the cilium-agent commandline flag --hubble-drop-events.

This issue can be used to collect feedback about the feature, the information it provides, and the scalability / performance impacts that it introduces.

Tasks

  • Define beta graduation criteria
    • Review output format (For example, drop reasons)
    • Review ratelimiting/QPS behaviour and maximum event emit rates per node
    • Enable in scale tests and assess impact with varying traffic drop rates
    • Validate behaviour with DDoS-style drop pattern
  • feedback improvements
    • consolidate event rate-limit / throttling flags, see this comment.
    • limit the number of policies shown in the message when --hubble-drop-events-extended is provided, see this comment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/hubbleImpacts hubble server or relayarea/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.kind/enhancementThis would improve or streamline existing functionality.pinnedThese issues are not marked stale by our issue bot.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.sig/scalabilityImpacts how well Cilium handles a high rate of events or churn.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions