Pass context to kube.Exec and similar functions. #25703 #249
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.
Currently, commands executed in pods are not aware of context state, and if context is cancelled they are still running.
This PR changes K10 code so that context is always passed to any kind of kube.Exec method.
There is related Kanister PR kanisterio/kanister#2878 which contains passing context right to the Kubernetes Executor.StreamWithContext which states "The context controls the entire lifetime of stream execution."