Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support sending signals on file change #23

Open
discordianfish opened this issue Sep 17, 2018 · 7 comments
Open

Support sending signals on file change #23

discordianfish opened this issue Sep 17, 2018 · 7 comments

Comments

@discordianfish
Copy link

Since Kubernetes 1.11 it's possible to share the IPC namespace, allowing to send signals between containers.
Since many services reload their config on a signal, e.g SIGHUP, it would make sense to add this to the configmap-reloader.

Specifically I like to reload fluentd on configmap change.

@gofman8
Copy link

gofman8 commented Dec 24, 2018

+1

@jimmidyson
Copy link
Owner

Great idea. Any thoughts on what flags would look like and how to figure out what process to send signal to?

@andrewhowdencom
Copy link

to the question specifically I would probably expect something like:

./bin pgrep 'nginx'

Or something. Bonus points - allow re-implementing pgrep semantics -- --user et. al.

Note: This is a substantial amount of work; this may have poor ROI.

@zgfh
Copy link

zgfh commented Oct 8, 2020

should we copy this ? https://github.com/lvelvis/nginx-config-reload

@marcbachmann
Copy link

marcbachmann commented Oct 27, 2020

I wrote my own script that supports custom shell scripts and therefore also signals.
It uses md5-based file comparison to detect changes on files:
https://hub.docker.com/r/livingdocs/file-change-hook

It's not really a solution for this tool, but it might help some people.

@AkaiNoCat
Copy link

1

@sinacek
Copy link

sinacek commented Mar 17, 2023

Is there any change, that will be implement this year?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants