litellm - 💡(How to fix) Fix [Feature]: Support tpl in podAnnotations in litellm-helm chart [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

When users provide their own ConfigMap by setting proxyConfigMap.create: false, the chart's built-in checksum/config annotation — which lives behind {{- if .Values.proxyConfigMap.create }} in deployment.yaml — is also disabled. As a result, changes to a user-managed ConfigMap no longer trigger a rolling restart of the LiteLLM pods, because nothing in the pod spec changes.

Fix Action

Fixed

Code Example

{{- with .Values.podAnnotations }}
{{- toYaml . | nindent 8 }}
{{- end }}

---

{{- with .Values.podAnnotations }}
{{- tpl (toYaml .) $ | nindent 8 }}
{{- end }}

---

podAnnotations:
  checksum/config: "{{ include \"my-umbrella-chart.litellm-config\" . | sha256sum }}"
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

Render Values.podAnnotations through Helm's tpl function (with the root context $) in deploy/charts/litellm-helm/templates/deployment.yaml, so users can embed template expressions inside pod annotations.

Concretely, change:

{{- with .Values.podAnnotations }}
{{- toYaml . | nindent 8 }}
{{- end }}

to:

{{- with .Values.podAnnotations }}
{{- tpl (toYaml .) $ | nindent 8 }}
{{- end }}

Motivation, pitch

When users provide their own ConfigMap by setting proxyConfigMap.create: false, the chart's built-in checksum/config annotation — which lives behind {{- if .Values.proxyConfigMap.create }} in deployment.yaml — is also disabled. As a result, changes to a user-managed ConfigMap no longer trigger a rolling restart of the LiteLLM pods, because nothing in the pod spec changes.

If podAnnotations supported tpl rendering, users could simply re-introduce the rollout-on-config-change behavior themselves:

podAnnotations:
  checksum/config: "{{ include \"my-umbrella-chart.litellm-config\" . | sha256sum }}"

Without tpl, the value is emitted as the literal string "{{ include ... }}", which is useless.

This change is backward compatible — plain-string annotation values pass through tpl unchanged — and is consistent with the rest of the chart: extraInitContainers, extraContainers (deployment.yaml:50,215) and the migrations job (migrations-job.yaml:40,99) are already rendered with tpl (toYaml .) $. The direct precedent is commit 87d7e86479 ("feat(helm): add tpl support to extraContainers and extraInitContainers"), which applied the same idiom in April 2026.

A PR with the template change and a matching helm unittest test case is ready to file.

What part of LiteLLM is this about?

Other (Helm chart — deploy/charts/litellm-helm)

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

(leave blank or fill in)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Feature]: Support tpl in podAnnotations in litellm-helm chart [1 pull requests]