litellm/helm/litellm-helm/tests
Yassin Kortam de80e3afe4
fix(helm): scale the classic chart's HPA out at the documented 60 percent CPU (#35975)
* fix(helm): scale the classic chart's HPA out at the documented 60 percent CPU

The litellm-helm chart shipped targetCPUUtilizationPercentage: 80, which is
unexamined helm create scaffold rather than a chosen number. It arrived packaged
with the stock minReplicas: 1, maxReplicas: 100, a commented-out
targetMemoryUtilizationPercentage: 80, and the boilerplate "such as Minikube"
comment, the same provenance as the 128Mi resource example this file just
corrected.

60 is the documented recommendation. The mechanism behind it is scale-up lag:
the chart's own startupProbe is failureThreshold: 30 times periodSeconds: 10, so
a replica can take up to 300 seconds to become ready, and a pod added at 80
percent utilization arrives minutes after saturation.

The memory target stays commented out on purpose. The prisma query engine's
resident memory is a high-water mark that ratchets to the pod's worst-ever write
and is never returned, so a memory-target HPA reads the largest write a pod ever
did rather than what it is doing now, and replicas ratchet up without scaling
back in.

hpa_tests.yaml carried its second suite after a YAML document separator, and
helm-unittest loads only the first document per file, so that suite never ran;
an assertion planted in it still passed. Fold it into the one live suite and add
coverage pinning the rendered CPU target, the absence of a memory metric by
default, and that overrides still take effect.

Bump the chart to 1.1.2, since rendered output changes for anyone running with
autoscaling enabled.

* fix(helm): bump litellm-helm to 1.1.3 after rebase onto 1.1.2

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-09-02 10:19:03 -07:00
..
billing_metrics_tests.yaml feat(proxy): push-based OTLP billable-request metering for enterprise deployments (#31592) 2026-07-15 12:12:52 -07:00
bundled_db_images_tests.yaml fix(helm): pin bundled postgres and redis to the bitnamilegacy images (#34963) 2026-07-28 16:19:20 -07:00
coordination_redis_tests.yaml feat(deploy): make coordination redis a first-class chart and terraform surface (#32662) 2026-07-10 16:16:09 -07:00
deployment_command_args_labels_tests.yaml refactor(helm): move litellm-helm chart to helm/ and drop deploy folder (#32234) 2026-07-07 15:18:33 +03:00
deployment_tests.yaml feat(helm): compose DATABASE_URL_READ_REPLICA from a reader host secret key (#37109) 2026-08-20 16:03:32 -07:00
hpa_tests.yaml fix(helm): scale the classic chart's HPA out at the documented 60 percent CPU (#35975) 2026-09-02 10:19:03 -07:00
ingress_tests.yaml refactor(helm): move litellm-helm chart to helm/ and drop deploy folder (#32234) 2026-07-07 15:18:33 +03:00
masterkey-secret_tests.yaml fix(helm): reuse the generated master key Secret on helm upgrade (#39219) 2026-09-01 17:45:59 -07:00
migrations-job_tests.yaml fix(helm): default litellm-helm to the ghcr.io/berriai/litellm image (#37491) 2026-08-19 16:04:20 -07:00
pdb_tests.yaml refactor(helm): move litellm-helm chart to helm/ and drop deploy folder (#32234) 2026-07-07 15:18:33 +03:00
service_tests.yaml refactor(helm): move litellm-helm chart to helm/ and drop deploy folder (#32234) 2026-07-07 15:18:33 +03:00