Skip to main content

Kubernetes: 7. Manual Scheduling

  • As new pod definition files are created, Kubernetes goes through them and looks for the property nodeName
  • If this property does not exist, then Kubernetes has the job of scheduling this pod
  • It then looks for the nodes that can host this pod and schedules it there
  • And the pod definition is updated with the nodeName where it is running
  • The property nodeName in the below definition file is optional.
  • If the property is specified then kubernetes automatically schedules the pod on the selected node. This is called manual scheduling.
  • Once the Kubernetes identifies the node on which to run, it creates a binding object that binds the pod with the node on which the pod will run

pod-definition.yaml
apiVersion: v1
kind: Pod
metadata:
    name: myapp-pod
    labels:
        app: myapp
        location: IN

spec:
    nodeName: node01
    containers:
    - name: nginx-container
      image: nginx
    - name: backed-db
      image: redis

Manual Scheduling
  • If the scheduler is not running or there is no scheduler in kubernetes, then pods will remain in Pending state
  • To run the pods, the definition file has to be updated to add the node on which the pod can run
  • Remember that Kubernetes does not allow a nodeName to be specified once the pod is created
  • So for manual scheduling, nodeName has to be added to the yaml file before creating the pod  
  • So if the pod is already created with no scheduler, then a bind object has to be created
  • This has to be converted to a JSON format and sent to Kubernetes as a POST API request, mimicking what Kubernetes actually does. 

pod-binding-definition.yaml
apiVersion: v1
kind: Binding
metadata:
    name: myapp-pod

target:
    apiVersion: v1
    kind: Node
    name: node01

-----------------
{
"apiVersion": "v1",
"kind": "Binding",
"metadata": {
    "name": "nginx"
},
"target": {
"apiVersion": "v1",
"kind": "Node",
"name": "node01"
    }
}
----------------------

curl --header "Content-Type:application/json" --request POST --data '{ "apiVersion": "v1", "kind": "Binding", "metadata": { "name": "nginx" }, "target": { "apiVersion": "v1", "kind": "Node", "name": "node01" }}' http://$SERVER/api/v1/namespaces/default/pods/$PODNAME/binding/

How to know if scheduler is running ?
Check the pods running in the kube-system namespace
Here there is no scheduler running, so Pods will not be scheduled in this kubernetes

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

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: 15. Multiple Schedulers

Custom Scheduler Kubernetes allows to create custom schedulers There can be multiple schedulers running at a same time apart from the default scheduler or A custom scheduler can replace the default kube-scheduler to become the default one So a few pods that requires additional checks apart from taints and toleration, node affinity can go through the custom scheduler before getting scheduled on the node Whereas the rest of the pods can go through the default kube-scheduler Create Custom Scheduler We can either download the kube-scheduler and run it as a service or alternatively create it using a static pod Below here we are downloading the binaries to run it The property scheduler-name is used to define the name of the scheduler, if not set then it will be defaulted to default-scheduler For your custom schedulers, update this property name to set a custom name for your scheduler For Static pods, the name can be updated directly in the pod-definition file Use kubectl create -f <pod-de...
Post a Comment
Read more

Kubernetes: 20. ConfigMaps

  A Java map is a object that maps key to value. The key has to be unique. Environment Variables Environment variables can be directly added into Pod definition file under specs.env array But they will be limited to only the pod for which they are added For new Pods, the environment variables have to be added again ConfigMaps ConfigMaps are a way of storing the data in key: value pair This data is then injected into Pods via the definition file The data injected can be created as environment variables in the pod Or the data is just injected as a file that then can be used by the pod Create ConfigMaps There are two ways to create the ConfigMaps like any other Kubernetes objects Imperative  Declarative Note that in the declarative way there is no specs , we instead have data section config-map APP_COLOR: Blue APP_ENV: Prod config-map-creation-imperative kubectl create configmap -> Imperative way of creating configmap <config-name> --from-literal=<key>=<v...
Post a Comment
Read more