<p>I'm trying to deploy an instance of <a href="https://github.com/Netflix/hubcommander" rel="nofollow noreferrer">hubcommander</a> in our kubernetes cluster. Unlike other apps we are running there, this app is using a <a href="https://github.com/yaron-idan/hubcommander/blob/develop/launch_in_docker.sh" rel="nofollow noreferrer">shell script</a> as an entrypoint, which launches the python process only after performing some bootstrap steps.<br>
This presents a problem because the child process running python is not printing logs to stdout, and so when I try to troubleshoot the process by using <code>kubectl logs &lt;pod&gt;</code> I get nothing but the logs written by the entrypoint script.</p>

<p>This behaviour is not reproduced locally, where running the container in the exact same manner shows logs from both the main and the child process.</p>

<p>Is there any way to tell the bash script to execute python in the same PID? or make it send logs to the same stdout?  </p>

Yaron Idan
<p>Eventually, I've found out the lack of logs has nothing to do with the creation of a child process.<br>
It was rather due to the fact python buffers output by default.<br>
Executing the process using the <code>'u'</code> flag solved the issue for me.</p>
