search

IBM / core-dump-handler

Save core dumps from a Kubernetes Service or RedHat OpenShift to an S3 protocol compatible object store
https://ibm.github.io/core-dump-handler/
MIT License
136 stars 40 forks source link

Add support for getting metadata from EKS #14

Closed No9 closed 3 years ago

No9 commented 3 years ago

Currently only the core file and the metadata that is sent to composer process from the OS is captured on EKS. This is because the OS on the node doesn't provide access to the crictl client. Investigation is needed to confirm if the crictl client is available on the machine but not in the PATH. If it's not available the two options are to copy a version of crictl to the machine as part of the deployment or to integrate with the crio service using a library.

No9 commented 3 years ago

crictl wasn't available on the machine to the agent now includes the crictl binary and copies it to the shared host folder with the flag --set daemonset.includeCrioExe=true Available as part of https://github.com/IBM/core-dump-handler/releases/tag/v4.2.0