5 ms·
Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments
- deleted 2y ago[deleted]
- ofrzeta 2y agoDoesn't seem to offer more insights than the Kubernetes docs.
- deleted 2y ago[deleted]
- LetMeLogin 2y agoTotally. Plus it's misguiding readers with different functionality and use cases. For example "Persistent Storage: StatefulSets provide persistent storage to their pods through Kubernetes PersistentVolumes". The thing is that STS doesn't do that. That's actually in POD definition.
- MuffinFlavored 2y agoI had no idea... probably shows I haven't hit an advanced enough use case. > why isn't a statefulset just a deployment/pod with PVC mounted? * StatefulSets provide predictable pod names and hostnames (pod-0, pod-1) * StatefulSets handle pods sequentially (0→1→2), ensuring proper cluster initialization. * StatefulSets maintain a consistent pod-to-PVC mapping even after pod rescheduling. * StatefulSets delete pods in reverse order,
- sitkack 2y ago"Come on!"
- belter 2y agohttps://youtu.be/rrlsS6n7mBo https://youtu.be/rrlsS6n7mBo
- vanillax 2y agoAgree. Its more confusion. PVC / PV are native to k8s not something part of statefulsets. In fact you _probably_ only need to use Statefulsets for databases. Which is probably going to be abstracted away with Operators.
- verdverm 2y agoIt's more about roll forward/backward and services with a master+replica or leader election. That PVCs are common in stateful sets is more a symptom than the cause
- vanillax 2y agoYea for sure. Thats why I dropped the term database because thats the exact scenario ( master / replica ) where pod consistency naming,dns, network etc is important for StatefulSet.
- null0pointer 2y agoAuthor is most likely farming credibility with blog spam.
- Abhisman 2y ago"Maybe readers would want to read what I've written" - That's the approach that I had in mind when writing the article.
- kevmo314 2y ago> Understanding the nuances and distinctions between these key concepts becomes crucial as you navigate the complex — yet rewarding — waters of container orchestration. Can't say I've ever felt rewarded for using Kubernetes, literally or metaphorically.
- smitelli 2y agoEarly on I heard the k8s controller ecosystem described as “a half dozen concurrent `while true` loops all fighting with each other.” Can’t say I disagree.
- pphysch 2y agoIsn't that distributed systems in a nutshell?
- nejsjsjsbsb 2y agoNode.js in a nutshell for sure
- ithkuil 2y agoIsn't that what we all are?
- seivan 2y ago[dead]
- draw_down 2y ago[dead]
- Abhisman 2y agoEh, dont you feel rewarded solving problems in general?
- kevmo314 2y agoCan't say I feel like Kubernetes has solved more of my problems than it created.
- dgfitz 2y agoI hope I've avoided containers enough to let this phase pass by. Formalizing vocabulary around the different states of a container makes me want to throw up my hands in a Seinfeld "come one" motion.
- Leo_Verto 2y agoLike it or not, containers are here to stay. They just make way too much sense as an atomic unit for delivering applicstions and really aren't that complicated. Kubernetes is a whole nother beast though and while it introduces a ton of overhead, it can be useful at a certain organisational scale as an API definition for delivering services to other teams.
- crabbone 2y agoThis isn't about the state of container. It's about interactions between several containers (a group of containers is called a pod). Which, probably, doesn't make it better for you, but for the sake of correctness...