Skip to content

[CWS] Track base mount namespace membership per image tag on MountNode - #529

Open
kovagsm wants to merge 1 commit into
masterfrom
mkovags/cws-mount-base-per-version
Open

kovagsm wants to merge 1 commit into
masterfrom
mkovags/cws-mount-base-per-version

Conversation

@kovagsm

@kovagsm kovagsm commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

What does this PR do?

Replaces MountNode.node_base and MountNode.base_namespace with map<string, MountSeen> seen, where MountSeen pairs ImageTagTimes with bool base_namespace. Regenerates the Go protobuf, vtproto, and Java bindings for the updated schema.

Motivation

A mount can belong to the base mount namespace in one version of a workload and only appear in a secondary mount namespace (for example, entered via setns or unshare) in another. A single boolean on MountNode conflates versions that share the same mount entry. Pairing ImageTagTimes with base_namespace per image tag in MountSeen records base-namespace membership per version while keeping NodeBase and ImageTagTimes free of mount-specific fields for all other node types.

Additional Notes

Fields 1 (node_base) and 6 (base_namespace) on MountNode are reserved so wire tags are not reused.

Describe how to test/QA your changes

Regenerated the Go protobuf, vtproto, and Java bindings from proto/cws/dumpsv1/activity_dump.proto. End-to-end encoding and decoding are exercised by the companion Agent PR (DataDog/datadog-agent#58006).

Replace MountNode.node_base and MountNode.base_namespace with a per-tag
map<string, MountSeen> seen that pairs ImageTagTimes with base_namespace,
keeping ImageTagTimes and NodeBase free of mount-specific fields.
@kovagsm
kovagsm force-pushed the mkovags/cws-mount-base-per-version branch from a92e532 to 2c24468 Compare October 15, 2026 13:41
@kovagsm kovagsm changed the title cws: track base mount namespace membership per image tag [CWS] Track base mount namespace membership per image tag on MountNode Oct 16, 2026
@kovagsm
kovagsm marked this pull request as ready for review October 16, 2026 13:41
@kovagsm
kovagsm requested a review from a team as a code owner October 16, 2026 13:41
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-16T13:43:08.216439Z 2c24468 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2c24468a55

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


message MountNode {
NodeBase node_base = 1;
reserved 1, 6;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve legacy mount fields during the rollout

When a receiver generated from this schema processes payloads from any already-deployed sender, fields 1 (node_base) and 6 (base_namespace) are now only unknown fields, so the receiver cannot access the mount's image-tag timestamps or namespace membership. Conversely, older receivers ignore the new field 7. This makes mixed-version agent/backend deployments silently lose mount metadata; retain the legacy fields as deprecated and support or dual-write both representations until old senders and receivers have aged out.

Useful? React with 👍 / 👎.

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.

1 participant