This message was deleted.

Let me ask maybe a more drilled down question. Is there a way to set a dynamic nodeSelector? For instance, say I can point to a label called

x-server: server-0

. Is there a way to get the

server-0

value from from another value in the chart? I guess, it would be possible, if I were to build the chart myself, but maybe there is a convention to reference somehow, I'm not aware of?

Just a thought to share. If you're able to get the dynamic value somewhere else, is it possible to do get the value into a variable, say varA. Then "helm upgrade chart --set x-server=$varA" ? The value specified in --set will overwrite default value that comes with the chart.

Yeah, thanks. But in the end, that won't work unfortunately. In general, I don't think I can get this to work with the helm chart as it is. I'm more than likely going to have to build out my own helm chart and make a deployment of the servers, so I can be more prescriptive with each replica and also be able to make assignments as needed via the Helm DSL.

You can use nodeselector for this: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/

@faint-island-31128 - Yes, I noted above about using nodeselector, but I'd need some sort of dynamic way to set the node selector and that is what is missing.

I don’t think I entirely understand your usecase then

It was a replica set in the Helm chart and why I couldn't "match up" PVCs. If a pod was restarted, it would land on any node and the volume it had created earlier would be missing. I've moved on from this problem, and to be honest, not sure how. LOL! 😊 I appreciate your chiming in.