Web Development Notes

Identify and Group Resources Meaningfully Kubernetes uses  labels  to describe resources and  selectors  to find them. Selectors come in two main forms: Equality-based selectors Set-based selectors Understanding when to use each is essential for scalable Kubernetes designs. Equality-Based Selectors Equality-based selectors match objects with  exact label key–value pairs . Supported operators: =  or  == !=  (CLI only) Example selector: matchLabels: app: color-api tier: backend This selector matches only Pods that have  both  labels. Set-Based Selectors Set-based selectors allow matching based on  sets of values  or  label existence . Supported operators: In NotIn Exists DoesNotExist Example: Multiple Values selector: matchExpressions: - key: tier operator: In values: - frontend - backend Example: Excluding Canary Releases selector: matchExpressions: - key: release oper...

Why StatefulSets Exist In Kubernetes,  containers are ephemeral by design . A Pod can be: Restarted Rescheduled to another node Deleted and recreated For many applications, this is perfectly fine. Stateless services (APIs, workers, frontends) don’t care  which  Pod handles a request. However, some applications  do care : Databases must keep their data Replicas may have leader/follower roles Nodes in a cluster may need predictable identities This is exactly the problem  StatefulSets  were created to solve. What Is a StatefulSet? A  StatefulSet  is a Kubernetes workload API object designed to manage  stateful applications  by providing  strong guarantees  around identity, storage, and lifecycle. Unlike a Deployment: Pods are  not interchangeable Each Pod has a  long-lived identity Each Pod gets  its own persistent storage Typical use cases: PostgreSQL, MySQL, MongoDB Kafka, Zookeeper, Elasticsearch Any replicated s...

  Overview Kubernetes provides different volume types depending on  how long data should live  and  where it should live . Two commonly confused options are: emptyDir local  Persistent Volumes Although both rely on  node storage , they behave very differently in terms of  lifecycle ,  scope , and  production suitability . emptyDir : Pod-Level Ephemeral Storage What is  emptyDir ? emptyDir  is an  ephemeral volume  that exists  only for the lifetime of a Pod . Created  when a Pod is scheduled to a node Deleted  as soon as the Pod is removed Initially  empty Shared between  all containers inside the same Pod Data strictly follows the  Pod lifecycle . Key Characteristics Scoped to  one Pod Cannot be shared across Pods Data is lost when: Pod is deleted Pod is rescheduled to another node Typical Use Cases Sharing temporary files between containers Caching data Scratch space Temporary processin...