AAP-46484 Capture k8s pod diagnostics - #1332
Conversation
bc6839f to
a56b3a7
Compare
lranjbar
left a comment
There was a problem hiding this comment.
Looking good! Just some feedback on these :)
78448c9 to
4ad6fde
Compare
4ad6fde to
55b3047
Compare
|
When a pod fails because the ephemeral-storage is over the limit I'm getting these error logs: I do see OOMKilled when the pod fails because of an OOMKill |
cb9a50b to
49afc98
Compare
Codecov Report❌ Patch coverage is
@@ Coverage Diff @@
## devel #1332 +/- ##
==========================================
- Coverage 51.60% 51.52% -0.09%
==========================================
Files 59 63 +4
Lines 9826 10491 +665
==========================================
+ Hits 5071 5405 +334
- Misses 4451 4776 +325
- Partials 304 310 +6
... and 9 files with indirect coverage changes
🚀 New features to boost your workflow:
|
PabloHiro
left a comment
There was a problem hiding this comment.
LGTM, thank you for the hard work!
|
davemulford
left a comment
There was a problem hiding this comment.
Reviewed during a 1:1 call, talked through some of the testing methods. Looks great!
| podName, | ||
| ) | ||
|
|
||
| // timeout := int64(10) |
There was a problem hiding this comment.
Take out commented out code please,
The tests are enough for now
| } | ||
|
|
||
| // only transition from WorkStateRunning to WorkStateSucceeded if WorkStateFailed is set we do not override | ||
| // pod, err := kw.KubeAPIWrapperInstance.Get(kw.GetContext(), kw.clientset, podNamespace, podName, metav1.GetOptions{}) |
There was a problem hiding this comment.
same as above
Take out commented out code please,
The tests are enough for now



Detect a pod failure caused by OOMKilled or other infrastructure related error.
This one outputs:
Note we have a new PR 1368 for CapturePodStatus