Nik Skoufis

@jcstanaway I think it's just at startup. The result is that if you leave a strategy running that stops nodes without restarting them (which is the sensible behaviour if you...

> Not sure if it helps, but it'd be fine if it was only allowed for alerts defined in the flux-system namespace. This would work for us. That said, I...

> lg, can you add default attempts doc. It is 2 by default. I thought attempts was a required field? Or is the behaviour that if you omit the whole...

Updated to document `attempts` and `retryRemoteLocalities`, as well as adding a note that indicates that retries are enabled by default

I've only updated the proto for `v1alpha3`. Should I be updating the `v1beta1` proto as well/instead?

Can somebody please add the `release-notes-none` label (I don't think this needs release notes)

/retest

> Can you make similar change to virtual service in v1beta1 as well? We need to keep both in sync. @linsun I've updated the docs for v1beta1. Do I also...

Just an FYI, we were encountering this issue on k8s 1.17, kube-proxy 1.16.13, aws cni 1.6.3 and 1.7.1. Turns out the issue was a bad PSP for `kube-proxy` that had...

@mogren this is on EKS, version 1.17. We discovered this as part of adding custom PSPs to all components. No scripts locking iptables on startup, using the standard EKS AMIs....