Debug School: Soumya

What is Daemon Set #3 By Soumya

Soumya — Wed, 18 Oct 2023 12:02:40 +0000

Daemon Set

1.  A Daemon Set is a type of workload in Kubernetes that ensures that one and only Pod runs on all nodes within a cluster, It is basically used for proxy kind of services.
2.  Daemon Sets ensure that exactly one instance of a specified Pod is scheduled and running on each node that matches the Pod's node selector.

Jobs

1. A job is something that runs the specified task using the container image provided in the template.
2. Once the task is completed successfully, the Job is considered finished.

Crone Jobs

1. Cron Job is a resource that allows you to run Jobs at scheduled intervals.
2. The job is created as a one-time Job when the schedule is met and then terminated.
3. The Schedule field is used to specify when the job should run i.e.(schedule: "*/5 * * * *"). In this case, it runs every 5 minutes.

Config Map

1. In Kubernetes, a Config Map is a resource that allows you to store configuration data separately from your application code.

Services

1. Service is also known as network load balancer.
2. Service only send traffic to healthy pods.
3. Services can be accessible from outside the cluster.
4. It uses TCP by default and load balancing is Random load balancing by default.
5. Service can be configured for session affinity.
6. The labels of pods should be same as the selector labels of service to balance the load.
7. Expose command automatically take the labels from deployment and create a service and balance the load.

Node Port

1. Node port create a service with cluster IP and type is node port which can be accessible from outside.
2. Node port is something which is used to communicate from outside to the pod.
3. To access the pod inside the cluster we need to give the Service IP : port and to access from outside we need to give Node IP.

Ingress Controller

1. An Ingress Controller in Kubernetes is a component that manages and configures access to services within the cluster from external network traffic. 
2. It acts as a reverse proxy, handling incoming HTTP and HTTPS traffic, and then forwarding requests to the appropriate services and Pods based on the rules defined in the Ingress resource.

What is Deployment #3 By Soumya

Soumya — Tue, 17 Oct 2023 11:54:18 +0000

Troubleshooting of pods.
A Replication Controller is one of the core components in Kubernetes that helps manage and ensure the desired number of replicas (Pods) are running and maintained within a cluster.
It is a primitive and has been largely replaced by the more advanced and flexible ReplicaSet and Deployment controllers in modern Kubernetes.
A ReplicaSet is a higher-level abstraction in Kubernetes that, like a Replication Controller, helps manage and ensure a desired number of replicas (Pods) are running within a cluster.
Deployment is the best practice to use for pod creation.
Deployment used rolling update policy for scaling by default.
Deployment is consists of replication, controller, versioning, rollout, rollback.
We can scale up the pods by using commands and all. 9.Namespace is a logical separation of cluster. 10.port forwarding can be done to forward the container port to the pod port.

What is POD #2 By Soumya

Soumya — Mon, 16 Oct 2023 11:51:33 +0000

Kubernetes consists of Master and Worker Nodes.
Master node contains API Server, Cluster Storage, Controller manager and schedulers.
The worker node contains kube-proxy, container engine and Kubelet.
Pods are the place where the one or more than one container is running.
To access the containers running inside the pods we need to access the pod IP.
If more than one container is running inside a pod is called tight coupling and if one container is running inside one pod is called loose coupling.
The best practice is to run one container inside one pod for unique port number.
The Pod is something which only holds the container in it,if a container stops the pod will not start.
We can use YML configuration files to create a pod.
Pod holds the configuration information that determine how a container should run.

Assignment #1 By Soumya

Soumya — Mon, 16 Oct 2023 07:29:09 +0000

What is Kubernetes?

Kubernetes is an open source platform that automates Linux container operations. It is and orchestration platform for scheduling and automating the deployment, management, and scaling of containerized applications.

Why Do we need Kubernetes? Explain in 10 lines.

Below are some reasons why we need Kubernetes :

Kubernetes is Self-healing.
Kubernetes is having storage orchestration.
Kubernetes can handle multiple container which can be running in a single node or in multiple nodes.
Kubernetes is having automated rollouts and rollbacks.
Load balancing is taken care by Kubernetes.
High availability is maintained by Kubernetes.
Kubernetes is a open source and easily available.
Managing the scaling of containers and clusters.
Deploying images and containers.
Kubernetes is able to store the configuration and security files as well.

How Kubernetes Works?

Kubernetes works by Master and Worker.
Master is the virtual machine which is present in one of the network and manages the workers.
The workers are the nodes those contains one or more than one pods in it.
Pods are the place where the one or more than one container is running. To access the containers running inside the pods we need to access the pod IP.

Kubernetes Architecture. Explain each component with one line.

1.Master
1.1 API Server : It is the Front-end to the control panel and exposes the APIs.
1.2 Scheduler : The scheduler is responsible for assigning work to the various nodes.
1.3 Cluster Storage : It is the persistent storage for cluster state and config.
1.4 Controller manager : The controller-manager is responsible for making sure that the shared state of the cluster is operating as expected.

2.Worker
2.1 Kubelet : It register nodes with cluster and instantiate a pod.
2.2 Container Engine : It is responsible for running of the container. Kubernetes supports multiple container engines and the default one is containerd.
2.3 Kube-Proxy : The Kube-proxy routes traffic coming into a node from the service. It forwards requests for work to the correct containers.