UPSTREAM: 38925: Fix nil pointer issue when making mounts for container #13269
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.
Fixes #13263
Upstream (not yet merged):
kubernetes/kubernetes#38925
Related:
kubernetes/kubernetes#34251
Currently, there exists a gap in the kubelet state where the
vol.Mounter
can benil
. This was somewhat addressed by kubernetes/kubernetes#33616 but even upstream is still seeing the gap.Simple check to protect against it is the previously excepted solution.
@smarterclayton @derekwaynecarr