[patch] increase NFD worker daemonset readiness check timeout#2261
Merged
Conversation
durera
reviewed
May 20, 2026
durera
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
nfd-worker daemon set is taking too long to stabilize in our FVTs. After checking the cluster, it was identified that rather than a problem with the nfd-worker itself, it was an issue with the timing since it was getting deployed after around 60 minutes. Therefore, the timeout has been increased to 90 minutes to guarantee that will not fail.
Test Results
It will require run in actual FVT to test.
Related issues