feat(topology): add support for custom topology keys #135
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.
Signed-off-by: prateekpandey14 prateek.pandey@mayadata.io
What this PR does:
Now user can label the nodes with the required custom topology, the cstor-csi driver will support all the node labels as topology keys.
Ideally we should label the nodes first and then deploy the driver to make it aware of all the labels that node has been configured.
If we want to add labels on the Nodes after CStor CSI driver has been deployed, a restart all the csi-node daemonset pods are required so that the driver can pick the labels and add them as supported topology keys.
How the changes has been tested :
Special notes for your reviewer:
Docs will added to cstor-operators repo
Checklist
documentation
tagrequires-upgrade
tag