Skip to main content

Kubernetes: 13. DaemonSets

Daemon Sets

  • DaemonSets are like replicaSet and deployment
  • While replicaSets and deployments makes sure that sufficient number of pods are running as defined in the replicas
  • DaemonSets make sure that atleast one pod runs on each node of the kubernetes cluster
  • If a new node is added to the cluster, DaemonSet automatically runs a pod on that node
  • Based on the node selector and node affinity rules, you can run DaemonSets only on targeted nodes
  • Some of the use cases of the DaemonSet are monitoring, log collector etc
  • Say you want to monitor pods running on the nodes, DaemonSet is perfect to make sure that monitoring agent is running via pod on every node
  • kube-proxy runs as a DaemonSet
  • DaemonSet definition file looks very similar to replicaSet definition
  • Before v1.12 kubernetes didnt had a way to create a pod on each node. The only way was to create a pod definition by setting the node name property
  • From v1.12 kubernetes now uses the combination of node affinity rules along with the daemon sets to schedule the pod on the node

daemon-set-definition.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
    name: monitoring-daemon-agent

spec:
    selector:
        matchLabels:
            app: monitoring-pod-agent
    template:
        metadata:
            labels:
                app: monitoring-pod-agent
        spec:
            containers:
            - image: omi-agent
              name: omi-agent-container


kubectl create -f daemon-set-definition.yaml 
-> Create daemonset using the definition file

kubectl get daemonsets
-> View existing daemon sets

kubectl describle daemonset <daemon-set-name>
-> Get more information of the daemon-set deployed
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