Alternative upload sink

[tjungblu]

(yet another follow-up to the conversations that triggered #44 + #47)

Our customer is in the Telco space and already has a so called "Element Management System" that allows to observe crashes and manage crash dumps. They would like to upload the dump there instead of an ObjectStore.

I don't really have a good understanding of what they can upload and how that works in detail yet, I just wanted to figure out if we can make the upload system more composable.

One solution that immediately came to me would be to have a configurable sidecar container in the DS (basically just config in helm and values.yaml) that can run inotify or poll on the coreDirectory and upload to where it should go.

[No9]

Yes. Today you should be able disable the default agent upload by setting the scheduler to be none and disabling the iNotify.
Something like this should work but would need to be tested.

schedule: "* * * * * *"
useINotify: false

You can then deploy your own uploader either as part of the chart or out of band.
If we are to support different uploaders more systematically we should probably look to move the deployment of the service into an init container and also consider how these can be configured within an operator.
Tagging IBM/core-dump-operator#1

[No9]

Commented in the new FAQ 58ef93d
Specifically https://github.com/IBM/core-dump-handler/blob/pod-logs/FAQ.md#how-should-i-integrate-my-own-uploader