Siyu Wang
Siyu Wang
Hey @cerebrate , looks like it failed to create a fsnotify watcher because of the kernel error `too many open files`. https://github.com/openkruise/kruise/blob/052979046e879fd1a7fae302d685b006229b6b13/pkg/webhook/util/health/checker.go#L115-L118 It is probably forbidden by the inotify limit...
/hold Just for test.
/close
IMHO, Kruise should not care about cloud providers. It just works on pure Kubernetes API. > The workaround is to have a kubernetes docker secret with the token and then...
> nodes can pull the docker image without worrying about the repository/registry authentication I'm not sure how it works... Maybe they have modified the code of EKS kubelet, which can...
/pinned
> but this doesn’t work for scaledown s right? @perek CloneSet [does support scaledown by spread constraints](https://openkruise.io/docs/user-manuals/cloneset#deletion-by-spread-constraints) with no WorkloadSpread. But Deployment doesn’t support it.
You might need to delete the existing WorkloadSpread and recreate all pod of the CloneSet (or recreate the CloneSet), for the existing pods have already been patched deletion-cost annotation. Then...
> Still, I really like the patch functionality of WS as it allowed for easier debugging and compatability with our current system. Understand. Do we have a plan to improve...