AWS Bottlerocket support

[psact]

When deploying the helm chart on bottlerocket nodes, it doesn't appear the containerd socket is available under /run. I made a modification to the helm chart locally to mount it, and everything seemed to work. I can make a PR with my changes wrapped in a conditional, but I'm not sure if there are other use cases for customizing where the socket exists based on the OS.

psact@10b6c33

[No9]

Hey @psact Thanks for the letting us know about this variant.
It's important for the project that we capture these scenarios.

Looks like an additional values override would cover this?
Something called values.aws.bottlerocket.yaml stored in https://github.com/IBM/core-dump-handler/tree/main/charts/core-dump-handler and containing the variables you set.

Also update the table in the chart README and we are good to go.
https://github.com/IBM/core-dump-handler/blob/main/charts/core-dump-handler/README.md#installing-the-chart

Edit:
As an aside I'm not sure how that is working for you as it seems to be setting the core dump location to be the docker socket?
If the change is to support a different container socket in CRIO I would have expected a change to be at .Values.daemonset.crioEndpoint

core-dump-handler/charts/core-dump-handler/templates/daemonset.yaml

Line 48 in a1ccae1

- name: CRIO_ENDPOINT

[psact]

I had set crioEndpoint: "unix:///run/dockershim.sock", and deployCrioConfig: true which seemed to work. I kept the default dump mount location at /var/mnt/core-dump-handler

I went ahead and added some parameters for mounting the host docker socket, and pushed to my branch.

https://github.com/psact/core-dump-handler/tree/bottlerocket-dockersock

I can open a PR if you would like.

[No9]

Ah now I understand - Thanks for clarifying and putting together the yaml file.
Happy to take this as a PR

[No9]

Fixed in V8.6.1
Thanks again for the PR