i have a bare-metal kubernetes cluster with 1 master node and 4 worker nodes. I want to deploy my deployment objects on every 4 worker nodes but i can't. I try nodeSelector but looks like it only works on last key:value pair label.
Please help me.
-
If you do nothing Kubernetes will decide where to place the pods, and things will usually wind up distributed around the cluster. Do you want something more specific than a default scheduling policy; if so, what and why?David Maze– David Maze2020-05-16 11:42:07 +00:00Commented May 16, 2020 at 11:42
Add a comment
|
1 Answer
If you want to ensure that all nodes have that pod on them you can use a DaemonSet.
You can also use affinity/anti-affinity selectors.
Inter-pod affinity and anti-affinity allow you to constrain which nodes your pod is eligible to be scheduled based on labels on pods that are already running on the node rather than based on labels on nodes. The rules are of the form “this pod should (or, in the case of anti-affinity, should not) run in an X if that X is already running one or more pods that meet rule Y”
If you don't want to two instances are located on the same host, check following link
