Skip to main content

Kubernetes: 11. Node Affinity

Scheduler

  • By default Pods gets scheduled based on node availability for the scheduler
  • There may be cases where in one of the node has more resources and the pod required to be scheduled on this node
  • There are two ways to achieve this
    1. Node Selector
    2. Node Affinity
Node Affinity
  • The primary purpose of node affinity is to make sure that pods are hosted correctly on the nodes
  • Assume that during pod creation the affinity rules match and the pod is created, what if the node labels are changed after the pod creation
  • What happens to pod depends on the nodeAffinity values set. These are
    1. requiredDuringSchedulingIgnoredDuringExecution
    2. preferredDuringSchedulingIgnoredDuringExecution
    3. requiredDuringSchedulingRequiredDuringExecution
  • 3rd option still does not exist in Kubernetes, it will be/or is already released in the future releases
  • Operators can be In, NotIn, Exists
  • For Exists, we don't need to specify any value in the pod-definition. This is because affinity rules only check if the key exists, it does not look for any values
pod-definition.yaml
apiVersion: v1
kind: Pod
metadata:
    name: myapp-pod
    labels:
        app: myapp


spec:
    containers:
    - name: nginx-container
      image: nginx

    affinity:
        nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
                nodeSelectorTerms:
                - matchExpressions:
                  - key: size
                    operator: In
                    values:
                    - Large
                    - Medium
  
How to force a pod to schedule on a node?
  • With taints & toleration, only the pod that can tolerate a taint gets scheduled on that node.
  • But the pod can be scheduled on a node that has no taint defined
  • With node selectors, only the pod that matches the with the node label gets scheduled on that node.
  • But a pod with no selector rules can be scheduled on a node with label
  • So a combination of taints and toleration along with node selector has to be used
  • With taint & toleration only pods that can tolerate the taint will be scheduled and
  • with node selector pod will be scheduled only on the node it is supposed to
Labels:

Comments

Post a Comment

Popular posts from this blog

Azure Active Directory

Azure Active directory (AAD) is a Identity as a Service. This is a smaller subset of Active directory. This is not a replacement to active directory at all. Azure active directory provides the identity services to the mobile apps and web apps in Private cloud. These apps may be connected to on-premise applications. So an SSO is enabled for these apps. So Azure active directory has very simple functionality. Create Users, Groups. Map groups to network security groups and provide the authentication to the resources. When you login to Azure portal, right upper corner of the screen has username along with the domain. Domain or tenant or organization are used interchangeably. Management of Users and Groups: Cloud identity (create users manually)  Directory synchronized identifiers (users are synchronized)  Add users Adding a cloud identity users makes the user as Guest When you do directory synchronization on Premise AD Groups are synched up wi...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more

Kubernetes: 5. Services

A  service  is a stable endpoint to connect to "something" An abstract way to expose an application running on a set of pods as a network service. Services enable communication between various components within and outside of the application With Kubernetes Services there is no need to configure the application for service discovery Kubernetes Service is an object just like Pod, ReplicaSet etc There is always a service running when Kubernetes is installed, Kubernetes API itself When a service is created, kubernetes creates the endpoints (kubectl get endpoints) The endpoints has all the pods associated with that service Headless Service A headless service is obtained by setting clusterIP  field to None Since there is no virtual IP address, there is no load balancer either The DNS service will return the pods' IP addresses as multiple A records This gives us an easy way to discover all the replicas for a deployment This is useful for creating stateful service...
Post a Comment
Read more