You are ready to deploy a new feature of a web-based application to production. You want to use Google Kubernetes Engine (GKE) to perform a phased rollout to half of the web server pods.
D is an interesting option, but a stateful set with parallel pod management policy seems overkill for a simple web server deployment. Isn't that more for stateful applications?
C is a nice idea, but a replica set alone won't give you the control you need for a phased rollout. I'd want something more specific to the deployment process.
B sounds interesting, but I'm not sure Node taints with NoExecute are the right tool for this task. Shouldn't we be looking at something more deployment-focused?
I think option A is the way to go. A partitioned rolling update allows you to gradually roll out the new feature to a subset of the pods, which seems perfect for this scenario.
Solange
1 months agoGlenna
1 months agoTijuana
1 days agoSocorro
3 days agoJutta
16 days agoJordan
18 days agoHarley
1 months agoLaurel
15 days agoCorinne
18 days agoMalcom
1 months agoLizette
2 months agoEric
9 days agoElouise
17 days agoFloyd
1 months agoLisbeth
2 months agoVicente
2 months agoRobt
2 months agoBarb
2 months ago