Add .command.log redirection in K8s container command when Fusion is not enabled #6455
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using k8s without Fusion the .command.log file is only saved if a task fails. However, Platform tries to get
.command.log
for all tasks executed. So for non-failed tasks it is unable to find the log file.This PR changes the container command to include the redirection of
.command.run
outputs to.command.log
when Fusion is not enabled. It replaces #6451 because getting .command.log from the pod logs for all tasks overload the Kubernetes API with large number of tasks.See also #2782
Tested with local K3d cluster: