09What does a Deployment give you that a ReplicaSet does not, and when would you touch a ReplicaSet directly?▼easyNewAmazon & AWSRed HatInfosysunlockedA ReplicaSet keeps a count. A Deployment manages a sequence of ReplicaSets, and that is the entire difference: it is what turns a change into a rollout you can pause and undo.Open full answer →
09The pipeline says the deploy succeeded, but users still see the old version. Find it.▼mediumGitLabAtlassianMeta2 notes & commentsunlockedA deceptively deep question, because there are at least six places a version can get stuck and they span the pipeline, the cluster and the edge. Work the path in order.Open full answer →
25A rolling update stalls halfway: new replicas crash-loop and old ones are already scaled down. What are your first moves?▼mediumFlipkartPhonePeSwiggy○ sign inThe reflex is rollback and it is usually right. Shared state, changed credentials and unavailable old artifacts can make an undo incomplete or unsafe. Verify those dependencies before choosing the recovery.Open full answer →
12PodSecurityPolicy was removed from Kubernetes. What replaced it, and how do you roll pod security out safely?▼mediumRed HatGitLabPhonePeunlockedNaming the replacement is the floor of this question. What scores is the audit-then-warn-then-enforce sequence and an honest answer about the vendor chart you cannot fix.Open full answer →
