fix: namespace DataVolume names per VM to prevent collisions#47
Merged
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrhillsman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
exe-prow-github-app
Bot
added
the
approved
mrhillsman
force-pushed
the
fix/datavolume-namespace-collision
branch
from
0152fbd to
e5c949c
Compare
DataVolume template names in disk.go and database.go were hardcoded without incorporating the VM instance name. When deploying multiple VMs via --vm-count > 1, all VMs referenced the same DataVolume name, causing Kubernetes API resource conflicts. This commit introduces a namespaceDataVolumes helper function that appends the VM name to DataVolume template names and updates the corresponding volume references. The function is called in both single-VM and multi-VM workload paths to ensure unique names. Fixes #3 Signed-off-by: Melvin Hillsman <mhillsma@redhat.com>
mrhillsman
force-pushed
the
fix/datavolume-namespace-collision
branch
from
e5c949c to
381195d
Compare
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
1 participant
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.
DataVolume template names in disk.go and database.go were hardcoded without incorporating the VM instance name. When deploying multiple VMs via --vm-count > 1, all VMs referenced the same DataVolume name, causing Kubernetes API resource conflicts.
This commit introduces a namespaceDataVolumes helper function that appends the VM name to DataVolume template names and updates the corresponding volume references. The function is called in both single-VM and multi-VM workload paths to ensure unique names.
Fixes #3