Skip to main content

Kubernetes: 14. Static Pods

Kubelet Service

  • Kubelet service is resposible for creating pods on the nodes
  • Kubelet service gets the request from kube-api server to create the pod
  • Kube-api inturn gets the request from scheduler to create the pod
  • Kube-api server then gets the data from etcd and sends the request to all the kubelet services running on the nodes
Static Pods
  • Kube-api service is not the only service that kubelet service listens to create the pod
  • kubelet service also looks into a specific folder on each of the node
  • In this folder if it finds the pod-definition yaml file, it will create the pods based on it
  • Note that Kubelet only creates a pod, if you have other objects like replicaSet, deployments etc it wont create those services
  • Services other than pods still have to come through kube-api service
  • Pods created by kubelet service looking into this configuration folder are called Static pods
  • They are not requested by kube-api service
  • But when you execute kubectl get pods, the output will show the static pods as well, even though they didnt originate from kube-api service
  • These pods shown from kubectl get pods output are read only pods, no changes can be made to them using kubectl edit or by deleting them
  • To make any changes to the static pods, update the definition file in the configuration folder and kubelet applies those changes
  • To delete the static pods, delete the definition file from the configuration folder and the kubelet deletes these pods
  • From the below kubelet service we can see the property pod-manifest-path=/opt/kubernetes/runconf that kubelet looks for creating static pods
  • Sometimes instead of pod-manifest-path, there will be a config property set in kubelet config.yaml file. staticPodPath property is set in this yaml file
  • kubelet will be running all the pod definition files under pod-manifest-path as static pods
  • Static pods will run in kube-system namespace
  • Static pods name will end with the hostname 
Static Pods vs DaemonSets
  • Static pods are created by kubelet service directly
  • DaemonSets are created by kube-api server
  • Static pods are used to create the control plane component like kube-api server, etcd, kube-scheduler, kube-controller
  • DaemonSets are used to create services that has to run on every node in the kubernetes cluster like kube-proxy, monitoring agents, logging agents etc
  • Unlike daemonSets staticPods cannot be managed with kubectl or other kubernetes API clients. Static Pods do not depend on the API server, making them useful in cluster bootstrapping cases.

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