dev-notes/docs/containers/kubernetes.md

Kubernetes (k8s)

Cluster Architecture

A Kubernetes cluster consists of a set of worker machines, called nodes, that run containerized applications. Every cluster has at least one worker node.

The worker node(s) host the pods that are the components of the application workload. The control plane manages the worker nodes and the pods in the cluster.
In production environments, the control plane usually runs across multiple computers and a cluster usually runs multiple nodes, providing fault-tolerance and high availability.

Control Plane

The conrtol plane is the container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers. It's components are:

• kube-apiserver: entrypoint of the cluster that exposes the kubernetes API
• kube-contoller-manager: keeps track of what is happening in the cluster
• kube-scheduler: ensures pod placement on the nodes based on node resource availability
• etcd: key-value store used as Kubernetes backing store for all cluster data

Note

: in production environment there are at least two control planes to ensure constant availability of thier functionalities

Node

Nodes are the worker machines in kubernetes. The node components are:

• kubelet: the agent that runs on each node in the cluster. It makes sure that containers are running in a pod
• kube-proxy: the network proxy paret of the cluster virtual network that allows communication to pods from inside or outside of the cluster
• conatiner runtime: the software that is responsible for running containers

Kubernetes Components

Pod

Pods are the smallest unit in kubernetes. They are an abstraction over a set of running containers. The pod abstarction is used to make kubernetes independet from the container technology.

Each pod has it's own IP address inside the virtual network of the cluster; this makes pod comunication possible.
Since pods are ephemeral resources when a pod dies another one will replace it. The new pod will get a new IP address.

Service

Services are permanet IP addresses and ar used to resolve the issue of changing pod IPs. Each pod can be atatched to a service. The lifecycle of a service is detached from a pod.
External services are used to make the contents of a pod accessible from the outside of the cluster while internal services are not exposed.

Ingress

Ingresses are the componentst hat forwards external requests to specific services. Ingresses are used to expose services through secure protocols and friendly URLs instead of service IPs.

ConfigMap

ConfigMaps are external configurations used to store non-confidential data in key-value pairs. Pods can consume ConfigMaps as environment variables, command-line arguments, or as configuration files in a volume.

ConfigMaps allow to decouple environment-specific configuration from container images, so that applications are easily portable.

Secret

Secrets contains a small amount of sensitive data such as a password, a token, or a key. Such information might otherwise be put in a Pod specification or in a container image.

Secrets are similar to ConfigMaps but are specifically intended to hold confidential data.

Because Secrets can be created independently of the Pods that use them, there is less risk of the Secret (and its data) being exposed during the workflow of creating, viewing, and editing Pods.

Warn: secrets, by dedfault, are not encrypted: they are stored in base64. Conside using third-party encryption tools.

Volumes

Volumes are physical storage attached to a pod in order to persist data when a pod is shut down.

Warn: kubernetes dows not manage data persistance. Backups must be managed externally.

Deployment

Deployments are a description of the desired state of the cluster. The deployment controller changes the actual state to match the desired one.

Deployments can be used to manage the scaling of the replicas of a pod.

ReplicaSet

ReplicaSets are groups of identical pods and are used to guarantee the availability of the replicated appliaction. ReplicaSets are used to manage stateless applications.

StatefulSet

StatefulSets are group of pods with guarantees about the ordering and uniqueness of the pods. StatefulSets are used to manage pods that need consistent state like databases.

DaemonSet

DaemonSets ensure the all or some nodes in a cluster run a copy of a specifc pod.

Jobs

Jobs create one or more Pods and will continue to retry execution of the Pods until a specified number of them successfully terminate.

As pods successfully complete, the Job tracks the successful completions. When a specified number of successful completions is reached, the task is complete.

---

Kubernetes Configuration

Each kubernetes configuration file is composed by 3 parts:

• metadata
• specification
• status (generated by k8s)

Note

: kubernetes config files are written in YAML

---

kubectl

kubectl get

kubectl config get-contexts  # list available contexts

kubectl get namespaces  # list namespaces inside current context

kubectl get pod -n|--namespace <namespace>  # list pods inside namespace
kubectl get pod [-n|--namespace <namespace>] <pod> -o|--output jsonpath='{.spec.containers[*].name}'  # list containers inside pod

kubectl exec

kubectl exec [-i|--stdin] [-t|--tty] [-n|--namespace <namespace>] <pod> [-c|--container <container>] -- <command>  # execute a command inside a container

kubectl logs

kubectl logs [-f|--follow] [-n|--namespace <namespace>] <pod> [-c|--container]  # get pod/container logs