When DukeDSClient is run inside a k8s container the progress bar isn't visible.
This is due to how logging works within k8s - It holds the output until a newline is printed.
The current progress bar rewrites the same line without adding a newlines as it progresses.
This means there will be no output until the upload or download operation is complete when running inside k8s.
When DukeDSClient is run inside a k8s container the progress bar isn't visible. This is due to how logging works within k8s - It holds the output until a newline is printed. The current progress bar rewrites the same line without adding a newlines as it progresses. This means there will be no output until the upload or download operation is complete when running inside k8s.