Live data from Hacker News

Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

abhisman.notion.site

21–30 of 30 posts

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#21

Earlier quoted context omitted.

Agree. 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.

It'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

Yea 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.

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#22
post #6

> 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.

Eh, dont you feel rewarded solving problems in general?

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#23
post #6

> 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.

Eh, dont you feel rewarded solving problems in general?

Can't say I feel like Kubernetes has solved more of my problems than it created.

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#24
post #8
post #6

> 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.

Early 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.

[dead]

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#25
post #11

Earlier quoted context omitted.

Totally. 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.

"Come on!"

https://youtu.be/rrlsS6n7mBo

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#26
post #13
post #8

Earlier quoted context omitted.

Early 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.

Isn't that distributed systems in a nutshell?

Node.js in a nutshell for sure

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#27

Earlier quoted context omitted.

Eh, dont you feel rewarded solving problems in general?

Can't say I feel like Kubernetes has solved more of my problems than it created.

Are you doing datacenter-scale deployment and configuration?

Re: Understanding ReplicaSet vs. StatefulSet vs. DaemonSet vs. Deployments

#29

Earlier quoted context omitted.

Are you doing datacenter-scale deployment and configuration?

Yup

And you don't think Kubernetes solves a lot more problems than it creates? Very interesting, I wonder what you're comparing to.
Post reply on HN