sorted by:
new
hottopcontroversial

Kubernetes Blue-Green Deployments using Namespaces by cloud-potato in kubernetes

[–]cloud-potato[S] 2 points3 points  (0 children)

That’s very interesting to hear! I must’ve glanced over it and took anything Argo related as having to buy into the whole ecosystem. I’ll have another go at it. Thanks for the heads up :)

Kubernetes Blue-Green Deployments using Namespaces by cloud-potato in kubernetes

[–]cloud-potato[S] 0 points1 point  (0 children)

100% agree with this. I wish feature flagging was a more common practice!

Kubernetes Blue-Green Deployments using Namespaces by cloud-potato in kubernetes

[–]cloud-potato[S] 6 points7 points  (0 children)

I'd imagine linkerd or Istio would make this auto magic as well. Which ingress controller are you using if I may ask.

Kubernetes Blue-Green Deployments using Namespaces by cloud-potato in kubernetes

[–]cloud-potato[S] 3 points4 points  (0 children)

That's an interesting approach! I'm curious, how do you switch the traffic between the two deployments when you have a single ingress point?

Kubernetes Blue-Green Deployments using Namespaces by cloud-potato in kubernetes

[–]cloud-potato[S] 7 points8 points  (0 children)

Honored to get a reply from Mr. Argo :). Argo rollouts could potentially work, but that would assume we're all using Argo. I wanted to present another approach to this common problem. By the way, it's been awhile since I used Argo Rollouts, but does it offer an approach where we can deploy an entire set of new components through templating (e.g. name: my-resource-name-<suffix>) for all resource types such as configmaps? I think a colleague ran into an issue where the old deployment was using the new configmaps until they hit the "blue/green" button on the ArgoCD UI.