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:

Comments

Post a Comment

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...
Post a Comment
Read more

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