I am using below configuration to log the abrupt disruption in pods using terminationMessagePath as terminationMessagePath: /tmp/message-log and terminationmessagePolicy as terminationMessagePolicy: FallbackToLogsOnError
but when the pods are getting restarted I am just seeing the path getting created as:
-rw-rw-rw- 1 root root 0 Sep 12 18:13 message-log
but file size is always of 0 byte.
Is this a bug in k8 version EKS 1.19