Debug School: Aravinda HB

Service Understanding

Aravinda HB — Mon, 25 Sep 2023 07:43:16 +0000

Service

In Kubernetes, a Service is a method for exposing a network application that is running as one or more Pods in your cluster

ClusterIP

Exposes the Service on a cluster-internal IP. This is the default Service type assigns an IP address from a pool of IP addresses that your cluster has reserved

NodePort

Exposes the Service on each Node's IP at a static port. Using a NodePort gives the freedom to set up our own load balancing solution, to configure environments that are not fully supported by Kubernetes, or even to expose one or more nodes' IP addresses directly.

LoadBalancer

Exposes the Service externally using an external load balancer. Kubernetes does not directly offer a load balancing component; we must provide one, or you can integrate your Kubernetes cluster with a cloud provider.

ExternalName

Maps the Service to the contents of the externalName field

Assignment-2

Aravinda HB — Fri, 22 Sep 2023 11:58:24 +0000

What is Namespaces? Explain with Image

Logical separation / division of resources based on Org / Project.

What is Pod? Explain with Image

A pod is the smallest execution unit in Kubernetes. A pod encapsulates one or more applications. Pods are ephemeral by nature, if a pod (or the node it executes on) fails, Kubernetes can automatically create a new replica of that pod to continue operations.

What is ReplicaSets? Explain with Image

A ReplicaSet (RS) is a Kubernetes object used to maintain a stable set of replicated pods running within a cluster at any given time. A Kubernetes pod is a cluster deployment unit that typically contains one or more containers.

What is Deployment? Explain with Image

A Deployment manages a set of Pods to run an application workload, usually one that doesn't maintain state.

Kubernetes - Assignment1

Aravinda HB — Thu, 21 Sep 2023 09:06:28 +0000

What is Kubernetes?

Kubernetes is a tool from Google introduced in 2014 mainly used for orchestration. Using K8s workload placement can be managed easily.

Why do we need it?

Container bring the scalability challenges, we cannot manage different hosts from docker,

How it works?

Kubernetes cluster will have master and worker nodes, master node will manage the entire cluster.
Request will be received from api server and an entry made in etcd. controller manager will monitor all the resources and scheduler will take care of allocating the node to the request made

What are the components of Master?

API server
Cluster Store
Controller Manager
Scheduler

What are the components of Worker?

Pod
Container