stefanprodan
commented
4 years ago Testing tasks and the gating API have nothing in common. I propose to split the two into separate services and deprecate the current loadtester app. For state persistence, the new gating service could implement external storage with Redis or Memcached, this way no matter how many replicas you would run, all of them will share the gate state.
When loadtester is deployed with 2 replicas, the state of a deployment's gate is localized to an individual loadtester pod. This leads to checks potentially providing an inconsistent state if queried multiple times.