Feature Request: Support initContainers for adding extra certificate stores

[flefevre]

Hi team,

I would like to suggest an enhancement to the LiteLLM Helm chart: the ability to define initContainers in the deployment.

Motivation:
Some users need to inject additional certificate stores or perform pre-start initialization steps in the container before the main LiteLLM process starts. Currently, the chart only supports extra environment variables and extra containers, but not init containers.

Proposed Solution:
Introduce a new values.yaml key, e.g., extraInitContainers, which allows users to define a list of Kubernetes init containers. These would be inserted in the pod spec before the main container(s). Example usage in values.yaml:

extraInitContainers:
  - name: init-certificates
    image: busybox
    command: ["sh", "-c", "cp /extra-certs/* /etc/ssl/certs/"]
    volumeMounts:
      - name: litellm-config
        mountPath: /extra-certs

This would then be rendered in the deployment template under spec.template.spec.initContainers, before the main container.

Benefits:

• Provides a flexible mechanism for pre-start initialization.
• Allows adding custom certificate stores or other initialization logic without modifying the main container image.
• Keeps the chart Helm-native and fully configurable via values.yaml.

I think this could be a useful addition for deployments that require custom certificates or other preparatory steps.

Thanks for considering this feature!