Anthropic → My kubernetes containers have some SIGTERM handling machinery that doesn’t seem
to trigger when the pod gets deleted. The same machinery triggers just ﬁne when I run
the container in docker locally and send the SIGTERM manually. Any guesses as to what
the issue is?

RLHF Response → Hmm that does sound weird... I think the most likely explanation is that the kubernetes con-
tainer runtime is not propagating the SIGTERM signal when the pod is deleted. The kubernetes
container runtime has its own lifecycle management algorithm that is different from docker,
and it probably doesn’t trigger the SIGTERM handling machinery when the pod is deleted.
You might need to look into conﬁguring custom SIGTERM handling in your kubernetes de-
ployment manifest. Hope that helps!

Anthropic → The Kubernetes docs make a big deal about SIGTERM being sent to the container before

deletion, you’re saying that doesn’t actually happen?
Training a Helpful and Harmless Assistant with Reinforcement Learning from Human Feedback