Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/2.0] Fix initial sync race when registering NRI plugins #11329

Merged

Conversation

klihub
Copy link
Member

@klihub klihub commented Feb 3, 2025

Update NRI deps to v0.8.0 and fix racy initial NRI plugin synchronization wrt. event processing by blocking plugin synchronization altogether during CRI event processing.

Notes: this PR does not pull in the latest tagged NRI version (v0.9.0) to keep the blast radius smaller. We can pull in NRI v0.9.0 if that is preferred. That would also pull in support for NRI WASM plugins and the related wazero and go-plugin dependency bits.

Block the synchronization of registering NRI plugins during
CRI events to avoid the plugin ending up in an inconsistent
starting state after initial sync (missing pods, containers
or missed events for some pods or containers).

Signed-off-by: Krisztian Litkey <[email protected]>
@dosubot dosubot bot added the area/nri Node Resource Interface (NRI) label Feb 3, 2025
@klihub klihub requested review from mikebrow and fuweid February 3, 2025 12:39
@fuweid fuweid merged commit be08040 into containerd:release/2.0 Feb 4, 2025
59 checks passed
@klihub klihub deleted the fixes/containerd/2.0.x/nri-plugin-sync branch February 4, 2025 15:29
@dmcgowan dmcgowan changed the title [release/2.0] fix initial sync race of registering NRI plugins. [release/2.0] Fix initial sync race when registering NRI plugins Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/nri Node Resource Interface (NRI) impact/changelog size/M
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants