Kubernetes
· 2 min read
Kinds
DaemonSet
- used to ensure that the same pod is running on all nodes in the cluster and that that pod is started before other pods
- Great for logging or management agents that need to run on every node
Deployment
- abbr:
deploy - used for reliability, load balancing and scaling
- creates a ReplicaSet
- uses declarative model
- allows you to perform rolling updates with zero downtime
ReplicaSet
- abbr:
rs - used to maintain a set of replica pods running at all times
- will add or delete Pod resources as necessary
StatefulSet
- Designed for stateful applications, and maintain a sticky identity for each of the pods
- Ideal for applications that need stable network identifiers, persistent storage, ordered deployment and ordered automated rolling updates.
Pod
- Abstraction over one or more containers
- One container for primary workload of the pod
- zero or more containers, called "sidecars"
- may provide additional functionality
- usually more cross-cutting concerns, e.g. observability
- zero or more containers, called "sidecars"
Service
abbr:: svc
- configures internal [[DNS]]
- uses
selectorfield to choose pods based on labels
Misc
Get pod logs
$ kubectl logs <pod-name>