Skip to content

HACK: report dataplane update events back to Typha for aggregation#10816

Closed
fasaxc wants to merge 5 commits intoprojectcalico:masterfrom
fasaxc:global-conv
Closed

HACK: report dataplane update events back to Typha for aggregation#10816
fasaxc wants to merge 5 commits intoprojectcalico:masterfrom
fasaxc:global-conv

Conversation

@fasaxc
Copy link
Copy Markdown
Member

@fasaxc fasaxc commented Aug 14, 2025

Description

Hackathon entry.

  • Send a new message from Typha to Felix with Typha's breadcrumb sequence number
  • Plumb that through Felix all the way to the dataplane and then report it back to Typha after each apply (with rate limiting).
  • In Typha, aggregate the stats and emit a histogram of dataplane apply latency every 10s.

Could lead on to:

  • Adding OTEL for Typha updates.
  • Adding prometheus metrics.
  • Figuring out when the whole cluster is fully converged.

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

TBD

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

@marvin-tigera marvin-tigera added this to the Calico v3.31.0 milestone Aug 14, 2025
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Aug 14, 2025
@fasaxc
Copy link
Copy Markdown
Member Author

fasaxc commented Sep 9, 2025

Productising part of this under #10918

@fasaxc fasaxc closed this Sep 9, 2025
@marvin-tigera marvin-tigera removed release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants