Cleanup old ReplicaSets after NetBox deployment patch to prevent volume Multi-Attach errors #345
Conversation
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
…me Multi-Attach errors
bruelea
approved these changes
Jun 30, 2025
vaishutin
pushed a commit
to vaishutin/netbox-operator
that referenced
this pull request
Aug 17, 2025
…me Multi-Attach errors (netbox-community#345) * Cleanup old ReplicaSets after NetBox deployment patch to prevent volume Multi-Attach errors * Updating size of NetBox persistent volume --------- Co-authored-by: Pablo Garcia Miranda <pablo.garciamiranda@swisscom.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
When deploying NetBox with
FORCE_NETBOX_NGINX_IPV4=true, the script patches the NetBoxDeploymentto mount a customnginx-unit.jsonconfig. This change triggers a new ReplicaSet and Pod, but the old ReplicaSet and its pod may linger during rollout.Since the NetBox pod uses a PVC with
ReadWriteOnceaccess mode, Kubernetes prevents simultaneous attachment to the new pod. This causes a volumeMulti-Attacherror and stalls the deployment.Solution
netboxdeployment