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

Comments

Popular posts from this blog

Kubernetes: 6. Imperative Commands

Imperative commands are useful in quickly creating the resources on Kubernetes kubectl --dry-run -> When created with this option, Kubernetes just validates the definition and does not actually create the resource -o=yaml -> Gets the output in YAML format kubectl run nginx-pod --image=nginx:alpine  -> Create a pod with name nginx-pod and image nginx:alpine kubectl run httpd --image=httpd:alpine  -> By default, run implies run-a-pod kubectl run redis --image=redis:alpine --labels=tier=db  -> Create a pod with name redis and image redis:alpine and labels set to tier=db kubectl run custom-nginx --image=nginx --port=8080  -> Create a pod with name custom-nginx and image nginx to run on port 8080 kubectl expose pod redis --port=6379 --name=redis-service  -> Create a service with name redis-service to expose pod named redis on service-port 6379 kubectl create deployment webapp --image=kodekloud/webapp-color --replicas=3  -> Create a depl...

Kubernetes: 21. Secrets

Passwords In the webapps we store the properties file for storing and retrieving the data required by application But we never store the application passwords, truststore, keystore passwords etc here We might store them in an encrypted format, but storing them as plain text is not the correct way In Kubernetes we store these sensitive information in Secrets https://medium.com/avmconsulting-blog/secrets-management-in-kubernetes-378cbf8171d0 Secrets Secrets are used to store the sensitive information They are similar to ConfigMaps, except that they are stored in hashed or encoded format Note that they are only encoded (using base64) but are not encrypted So secrets are a safe option to store sensitive information but infact they are not the safest option As such secret objects should be not checked into source code tools, its best to store them encrypted at REST in ETCD Again as in ConfigMaps, we have to create the secrets object first and then inject them into the pods There are 2 ways ...

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...