Mark Robinson

@jessesuen Ah, I see. We don't use `spec.minAvailable`, we just have `maxUnavailable` set as a percentage. ``` strategy: canary: ... dynamicStableScale: true maxSurge: 25% maxUnavailable: 10% ``` Do we need...

@zachaller I haven't had a chance to try it yet

@harikrongali I've attached the Rollout manifest. I can attach others if they'd be useful. We're using LinkerD as the service mesh topology in the cluster. [rollout.txt](https://github.com/argoproj/argo-rollouts/files/8781705/rollout.txt)

@perenesenko Here's the full rollout object [rollout.txt](https://github.com/argoproj/argo-rollouts/files/8828458/rollout.txt) What I can figure happened is that we had a networking problem causing 30 pods to fall off being ready (either the node...

Absolutely there are some work around but one you move off easy powers of 10. Let's say I wanted to alert on 90% of 2TiB, 2TiB != 2TB and there...

@ryanbr I'm not sure I understand your question. The site where `znsrc.com` is hosted? Where gem is hosted?

I would personally use enhanced fan-out in my system

It might be worth covering the use case for services that don't have ingresses. I'm thinking of a service that pulls from kinesis. This is common enough that it'd be...

@ju187 You could use the Job analysis type - https://argoproj.github.io/argo-rollouts/analysis/job/. You could write a load generate with k6 - k6.io - and package it up as a image to run...

@zachaller The bug doesn't reliably happen. So I can test this out but it might take a while to get feedback. My concern is that this PR is built on...