feat(CSI-259): report mount transport in node topology #337
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.
TL;DR
Added support for scheduling workloads by transport protocol (NFS or WekaFS) using node topology.
What changed?
NFS.md
documentation to include information about scheduling workloads by transport protocol.getTransport()
method for both NFS and WekaFS mounters.NodeGetInfo
function to include transport type in node topology.How to test?
pluginConfig.mountProtocol.allowNfsFailback=true
Why make this change?
This change allows administrators to optimize workload placement based on the available transport protocol. In hybrid deployments where some nodes have the Weka client installed and others don't, storage-intensive workloads can be directed to nodes with WekaFS transport, while more generic workloads can use NFS transport. This flexibility enhances performance and resource utilization in diverse Kubernetes environments.