Define the STOPSIGNAL in haproxy-keepalived image.
Why is this change being made?
Kubernetes must be told explicitly what signal to use; by default the stopsignal is SIGUSR1 and it should be SIGTERM.
How was this tested? How can the reviewer verify your testing?
Local test: built image, launched under helm, then helm delete haproxy-keepalived. Can now see the log message Received SIGTERM prior to container shutdown. (Still not working fully, though - the VIP isn't getting torn down despite the script apparently reaching the correct function.)
Completion checklist
[x] The pull request is linked to all related issues
Summary of Changes
Define the
STOPSIGNALin haproxy-keepalived image.Why is this change being made?
Kubernetes must be told explicitly what signal to use; by default the stopsignal is
SIGUSR1and it should beSIGTERM.How was this tested? How can the reviewer verify your testing?
Local test: built image, launched under helm, then
helm delete haproxy-keepalived. Can now see the log messageReceived SIGTERMprior to container shutdown. (Still not working fully, though - the VIP isn't getting torn down despite the script apparently reaching the correct function.)Completion checklist