11–20 of 30 posts
Doesn't seem to offer more insights than the Kubernetes docs.
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.
I 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.
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.
> 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.
Doesn't seem to offer more insights than the Kubernetes docs.
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.
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.
I 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 r…
> 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.
I 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.
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.
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.
Doesn't seem to offer more insights than the Kubernetes docs.
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.
> 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.