Based on Kubernetes' troubleshooting guide [1], it would be helpful if the sonataflow application could write to /dev/termination-log file the shutdown reason. It could be a failure or a success message. Either way, this message could be structured in JSON format, for example:

{
   "message": "Failed to start Quarkus application (...)",
   "type": "Error",
   "dateTime": "2023-08-09 18:30:00",
   "code": 123435
}

We just have to respect the 4096 bytes limit imposed by Kubernetes.
 

  [1] https://kubernetes.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/

 
Additionally, this feature should be configurable, for example:

kogito.app.terminationPath=/home/luke/mylogs/termination-file