### Check for existing issues

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

### The Feature

Currently the litellm helm chart (`/deploy/charts/litellm-helm`) does not provide a way to set `priorityClassName` to deployment manifests.

The implementation for this would be as simple as adding to the deployment template:

``` spec: template: spec: {{- with .Values.priorityClassName }} priorityClassName: {{ . }} {{- end }} ```

and in the values.yaml: ``` priorityClassName: "" ```

The equivalent can also be done in the other helm chart (`/helm/litellm`)

### Motivation, pitch

This is useful in protecting litellm from resource pressure evictions which can be common in Kubernetes environments. While these values can be added after the initial deployment, it runs the risk of being reconciled when using CD tools that sync against the chart (like via ArgoCD)

### 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_