Deployments in #kubernetes 🧵
Deployments are a high-level concept that manage ReplicaSets, similar to how ReplicaSets manage Pods.
Instead of directly trying to manage ReplicaSets or worse, Pods! You should only be using Deployments (1/4)
A deployment definition consists of the following fields:
1. Kind: Specifies Deployment as a resource type
2. Metadata: used to assign a name to uniquely identify this deployment object
3. Spec: the desired state for this deployment object e.g. the number of replicas (4/5)
Looking back on KubeCon + CloudNativeCon North America 2022 https://t.co/IOrx8vwP7W #cncf via @CloudNativeFDN
It's good to have @pritianka sharing her thoughts about the last @KubeCon_ NA in Detroit👏
@MichaelCade1@datadoghq More tutorials and helping material needed for other container runtimes within Kubernetes. Most examples I find on the internet are all using Docker.
4. Kind: specifies the ReplicaSet set as a resource
ReplicaSets are the basis for achieving one of the key feature of #Kubernetes ; self-healing applications (5/5)
ReplicaSets in #Kubernetes 🧵
A #ReplicaSet clones pods and ensures a specified number of pod replicas exist all the time in the cluster. Usually these copies exist on different nodes.
(1/5)
A ReplicaSet definition consists of the following fields:
1. Selector: identifies the pod this ReplicaSet will replicate
2. Replicas: specifies the number of replicas this ReplicaSet will maintain
3. Template: the pod template used by the ReplicaSet to create pods (4/5)
Pods in #Kubernetes 🧵
A pod is the smallest unit that can be deployed in a Kubernetes cluster. It consists of one or more application containers that share resources and local network (1/5)