kubectl run --attach proved to be rather unreliable. It often was not able to attach to the newly created pod. There were various different error messages. Ranging from pod not found to cutoff log outputs.
By running the pod, waiting and then printing the logs, it improved the reliability by a lot. Where it previously failed ever so often, I was not able to have it fail once with the new function so far.
Checklist
For Code changes
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] PR contains the label area:operator
[x] Link this PR to related issues
[x] I have not made any changes in the charts/ directory.
Summary
kubectl run --attach
proved to be rather unreliable. It often was not able to attach to the newly created pod. There were various different error messages. Ranging frompod not found
to cutoff log outputs.By running the pod, waiting and then printing the logs, it improved the reliability by a lot. Where it previously failed ever so often, I was not able to have it fail once with the new function so far.
Checklist
For Code changes
bug
,enhancement
,documentation
,change
,breaking
,dependency
as they show up in the changelogarea:operator
charts/
directory.