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

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