Christian Hopf

We would be happy to receive a PR for this. It seems to be a useful feature 👍

@jorgelon Do you see the following warn-log in the kured-pod-logs? ``` sentinel command ended with unexpected exit code ``` This was added with 1.14.0. The problem with the host-commands is:...

Okay, that's sad. Then it will be very hard to figure out why the file is not detected. Kured logs the output of the "test -f" command and logs a...

@fa-at-pulsit I strongly disagree to implement such a logic in kured. This would mean that kured would change the settings of all PDBs in a way, that they loose there...

Thanks @jorgelon for coming back to this thread, with 1.15.0 the nsenter on the hosts `/var/run/reboot-required` is not required anymore. You have two options now: 1. Use the `kured-ds.yaml` with...

The binary is not called inside the pod, its called with `nsenter` on the host. Does the problem persist with the "signal" method and the helm-chart? Does the pod still...

But this only would work, if you can use binaries which are already inside the kured-image right? So maybe you use a custom-image?

Thanks for the explanations. Yes, both binaries are already present. For the path-based method we could just create a file with go-code at a configurable, mounted location. Shutdowns are not...

Thanks for the hint, I did a review.

Main challenge is, that Prometheus is not aware of silences which are made in Alertmanager. To make this work we would also have to integrate Alertmanager in kured for checks.