Skip to content

Conversation

@isibeni
Copy link
Member

@isibeni isibeni commented May 9, 2025

Add support to configure the MaxVolumesPerNode value within the NodeGetInfo response.
Value can be configured using the MAX_VOLUMES_PER_NODE environment variable

@isibeni isibeni force-pushed the limit-mounts-per-volume branch from d5e62d4 to 832ae0a Compare May 9, 2025 15:05
isibeni added a commit to isibeni/ibm-object-csi-driver-operator that referenced this pull request May 9, 2025
Add support to configure MaxVolumesPerNode setting of csi node via the cos-csi-driver-configmap.
The configmap value will be synced to the CR
The node syncer will then update the MAX_VOLUMES_PER_NODE env var on the daemonset

Depends on IBM/ibm-object-csi-driver#173

Signed-off-by: Benjamin Isinger <[email protected]>
Add support to configure the MaxVolumesPerNode value within the NodeGetInfo response.
Value can be configured using the MAX_VOLUMES_PER_NODE environment variable

Signed-off-by: Benjamin Isinger <[email protected]>
@isibeni isibeni force-pushed the limit-mounts-per-volume branch from 832ae0a to d89436e Compare May 9, 2025 15:15
isibeni added a commit to isibeni/ibm-object-csi-driver-operator that referenced this pull request May 9, 2025
Add support to configure MaxVolumesPerNode setting of csi node via the cos-csi-driver-configmap.
The configmap value will be synced to the CR
The node syncer will then update the MAX_VOLUMES_PER_NODE env var on the daemonset

Depends on IBM/ibm-object-csi-driver#173

Signed-off-by: Benjamin Isinger <[email protected]>
@isibeni isibeni closed this Sep 8, 2025
@isibeni
Copy link
Member Author

isibeni commented Sep 8, 2025

Has already been implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant