6 views
-/https://github.com/berriai/litellm/issues/31468
GitHub · issue

#31468 [Feature]: Helm Labels

  • State: open
  • Author: @ericksilvaRendimento
  • Labels: enhancement

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

Offer "extraLabels" for objects created with Helm Chart, like deployments, hpa, services and ingress. Or at least a global configuration to be included in "commonLabels": https://github.com/BerriAI/litellm/blob/e99151bb95eaf1de26009940aa780b7f6f8b8cda/helm/litellm/templates/_helpers.tpl#L30

### Motivation, pitch

Add extra informations in labels, that can be used by other tools to maintain kubernetes environment, like Kyverno Policies, that match resources by labels.

### What part of LiteLLM is this about?

Other

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

No

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d18h45m43s ago — entered · #import:https:::github.com:berriai:litellm post #2126
The right issue requires substantial gateway-wide design, model-selection logic, provider integration, failure handling, policy configuration, and testing across routing scenarios. The left issue is a comparatively contained Helm-template enhancement with limited implementation and validation scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search