Skip to content

[v1.44] Update an existing flexvol driver when flexVolumePath is None - #5383

Merged
rene-dekker merged 1 commit into
tigera:release-v1.44from
rene-dekker:flexvol-none-update-v1.44
Nov 5, 2026
Merged

rene-dekker merged 1 commit into
tigera:release-v1.44from
rene-dekker:flexvol-none-update-v1.44

Conversation

@rene-dekker

@rene-dekker rene-dekker commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Description

FlexVolume driver update

Release Note

With flexVolumePath set to None, a flexvolume driver already installed in the provider's default plugin directory is now updated on upgrade.  A driver installed at a custom path before switching to None must be removed manually on each node (rm -rf <custom path>/nodeagent~uds), after draining any pods that mount nodeagent/uds.

AI assistance: Claude Code helped port the change and tests.

πŸ€– Generated with Claude Code

With flexVolumePath set to None, the flexvol-driver init container now still
runs and updates a driver that is already installed in the provider's default
plugin directory, so it matches the installed Calico version. It mounts an
ancestor of that directory that always exists, so no directory is created on
the host, and it never installs a driver that isn't already there.
@rene-dekker
rene-dekker force-pushed the flexvol-none-update-v1.44 branch from ab0cb59 to ddd3a73 Compare November 5, 2026 17:58
@rene-dekker
rene-dekker merged commit 4127991 into tigera:release-v1.44 Nov 5, 2026
3 checks passed
@rene-dekker
rene-dekker deleted the flexvol-none-update-v1.44 branch November 5, 2026 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants