Currently the mechanism used to keep track of what data is where is a nodeAffinity. This causes a few problems:
If a node in the list goes away, or a node is added, the list must be reconciled
Pods spawned by templates will not get the updated list, causing uneven distribution of pods.
A better approach to this is to manage affinity by tagging nodes with labels reflecting the kvc volumes. This way pods can always be matched to the data with a freshly reconciled node list.
Currently the mechanism used to keep track of what data is where is a nodeAffinity. This causes a few problems:
A better approach to this is to manage affinity by tagging nodes with labels reflecting the kvc volumes. This way pods can always be matched to the data with a freshly reconciled node list.