📄️ Myth: Rolling Updates Are Only Supported by Deployments
Many believe that rolling updates are an exclusive feature of Kubernetes Deployments. This assumption leads to the misconception that StatefulSets and DaemonSets do not support rolling updates, forcing teams to use workarounds. But is this really the case?
📄️ Myth: DaemonSet always schedule pods on all nodes.
Expect DaemonSet to Run on Every Node? Not So Fast! Many assume that a DaemonSet automatically schedules a Pod on every node in the cluster. While this is generally true, there are several cases where DaemonSet does not schedule Pods on all nodes.
📄️ Myth: Deployment Supports All Pod Restart Policies
Can You Use Any Restart Policy in a Deployment?
📄️ Myth: Kubernetes Automatically Deletes Old ReplicaSets
A few years ago, while troubleshooting a production issue, I ran kubectl get rs and noticed a long list of ReplicaSets—some created months ago.
📄️ Myth: Kubernetes Automatically Roll Back Failed Deployment
A team deployed a new version of their application, expecting Kubernetes to roll it back automatically if something went wrong. Unfortunately, the deployment failed, but instead of rolling back, Kubernetes left it in a bad state. The team was surprised—wasn't Kubernetes supposed to handle this automatically?
📄️ Myth: Kubernetes always injects information about Services into a Pod
I was attending a free Kubernetes webinar where the speaker was walking through service discovery patterns.
