Kubernetes

Kubernetes provides robust mechanisms for managing storage, allowing applications to store data persistently, independent of their lifecycle. Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) are the kubernetes concepts which relates to the persistent storage for the pods.

Kubernetes Admission controllers are the gatekeepers that ensure every request follows your specific rules for security, governance, and configuration.

DNS resolution in Kubernetes can be customized per pod and dnsPolicy in the pod spec allows different ways to configure how DNS resolution will happen inside the Pods.

In Kubernetes, there are mainly three types of probes (health checks) are used:
1. Readiness Probe
2. Liveness Probe
3. Startup Probe

In Kubernetes, a Horizontal Pod Autoscaler (HPA) automatically updates a workload resource (such as a Deployment or StatefulSet), with the aim of automatically scaling the workload to match demand.

You might have heard or used kubectl proxy and/or kubectl port-forward commands while working with Kubernetes cluster.
However, are you aware of how they work and when we should use the above commands?

Finalizers are namespaced keys that tell Kubernetes to wait until specific conditions are met before it fully deletes kubernetes resources.

Projected Volumes in Kubernetes maps several existing volume sources such as Secrets, Configmap etc into the same directory.

An admission controller is a piece of code that intercepts and processes requests to the Kubernetes API server prior to persistence of the object, but after the request is authenticated and authorized.

Priority Classes in Kubernetes are used to prioritize workloads to have a higher priority over the other ones. This property can be used for providing a higher priority to mission critical workloads so that they can continue running as much as possible.