Vivek Thomas

It appears Github has paused the plan to sunset the deprecated API -- https://github.blog/changelog/2022-03-04-paused-sunset-of-deprecated-teams-api-endpoints/

We'd be interested in this as well, we have some applications which we run with a graceful termination threshold of upto 3 hours. In most cases the pods gracefully terminate...

I've been running into something similar as well, mostly when my internet connection fails-over to backup. My ISP disconnects the PPPoE session every 24 hours so there is usually a...

So looking at the code a bit more, if `reclaimRemovedPeers` returns an error, a `FATAL` error is logged, which I think would cause that process to exit? https://github.com/weaveworks/weave/blob/34de0b10a69c2fa11f2314bfe0e449f739a96cd8/prog/kube-utils/main.go#L286-L289 `kube-utils` `reclaim-daemon`...

Ran into the same issue randomly even without the masters being rolled. There probably was a short network blip that caused a request from the reclaim daemon to timeout and...

This doesn't appear to be Weave related though, https://www.docker.com/increase-rate-limit might be more helpful. It is possible that you are pulling `weave` and `redis` images without setting the image pull secrets...

We've also seen something similar (more details in https://github.com/weaveworks/weave/issues/3910). Are you seeing only DNS resolution failures or are there other connectivity issues too? How big of a cluster is this...

/remove-lifecycle stale

> Also observed that when the existing CA pod is deleted manually , forcing a new CA pod comes up the pending pods get scheduled. > We've noticed this as...

/remove-lifecycle stale