can we mention more than one node label in single nodeSelector in kubernetes

i want to schedule 10 pods in two specific node(total 15 nodes in our kube cluster).

so in replication-controller file i am mentioning two values in nodeSelector
like below.

  • Problems trying to install docker compose on Kubuntu 16.04
  • docker-sync excludes are not excluded?
  • Config file for Neo4j Docker Image
  • Unable to locate runnable browser in Docker container
  • Extend docker devicemapper loop-lvm sparse file
  • Install PHP7 fpm and memcached with Docker
  • nodeSelector:  
      app: node1  
      app: node2  

    problem is that all the time it’s taking only node2.whatever sequence i am mentioning, it’s taking last node only.

    note: node1 and node2 are lables of node.

  • Debian Jessie - font € sign is rendered as fi ligature
  • Deploying a minimal flask app in docker - server connection issues
  • Docker registry --insecure-registry not working
  • Crontab doesn't have credentials
  • docker-compose.yml file behaves differently on ECS than local docker-compose
  • Creating a Docker UAT/Production image
  • 2 Solutions collect form web for “can we mention more than one node label in single nodeSelector in kubernetes”

    Yes, you can.

    If you want the pods to be scheduled to either node1 or node2, you may label both nodes with the same label(s) (for example, app=node), and then add app=node as your nodeSelector. You can add as many labels as you want, but like CJ mentioned, nodeSelector is a map with key and value pairs so it can’t have the same key with different values.

    The pods can be scheduled on any of the nodes that satisfy that nodeSelector.

    For more information, read Assigning Pods to Nodes. Note that there’s a new feature called nodeAffinity that you might also want to try.

    The nodeSelector on a PodSpec is just a map[string]string (instead of the more featureful NodeSelector type that is used in the NodeAffinity object).That means that the key “app” can only have one value, and it ends up being overwritten as “node2”.

    You can accomplish the scheduling between node1 and node2 by applying a common label (e.g. scheduling-group: foo), and then have your replicationController use that label as the nodeSelector.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.