Please add support for Kubernetes `initContainers

[Shemarr]

What would you like to be added?

Support for Kubernetes initContainers in Holmes, so an initContainer can fetch an API key at startup (e.g., from a secret manager/internal endpoint) and share it with the main Holmes container via a mounted volume.

Why is this needed?

Because the Holmes API key must be fetched dynamically at runtime (it can’t be hardcoded in manifests). An initContainer is required to retrieve the key from our secret source before the main Holmes container starts, write it to a shared volume, and allow Holmes to start with the key available. Without initContainer support, Holmes can’t run in environments where secrets are injected this way.

[aantn]

Hi @chehine-hub, can you share an example of another helm chart that implements this? It'll help us get it right on the first go!

[Shemarr]

Sure, we can do something like this to add init container support (to add it in the deployment helm template) :
{{- if .Values.initContainers }}
initContainers:
{{- toYaml .Values.initContainers | nindent 6 }}
{{- end }}

We need also to add custom args :
{{- if .Values.args }}
args: {{ toYaml .Values.args | nindent 10 }}
{{- end }}

[aantn]

@Shemarr can you test this please and confirm it works for you?

https://github.com/HolmesGPT/holmesgpt/pull/1516/changes