Skip to content

docs: update KEDA autoscaling guide to use integrated monitoring sub-chart#965

Merged
ruizhang0101 merged 3 commits into
vllm-project:mainfrom
asalah6:docs/update-keda-autoscaling-monitoring
Jun 19, 2026
Merged

docs: update KEDA autoscaling guide to use integrated monitoring sub-chart#965
ruizhang0101 merged 3 commits into
vllm-project:mainfrom
asalah6:docs/update-keda-autoscaling-monitoring

Conversation

@asalah6

@asalah6 asalah6 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Since v0.1.11 (PR #860), monitoring (kube-prometheus-stack, prometheus-adapter) is available as an optional sub-chart dependency. The KEDA autoscaling tutorial still references the old observability/install.sh script which is no longer the recommended approach.

This PR updates the documentation to reflect the new integrated monitoring setup.

Changes

  • Replace cd observability && bash install.sh with values.yaml configuration (enable kube-prometheus-stack and serviceMonitor in values)
  • Update Prometheus service addresses to match sub-chart naming convention (<release-name>-kube-prometheus-stack-prometheus)
  • Add note about using existing external Prometheus stacks (only serviceMonitor.enabled: true needed)
  • Update version requirement from v0.1.9+ to v0.1.11+
  • Update cleanup section to reflect new approach (disable in values instead of running uninstall script)
  • Add reference to PR feat(helm) add monitoring conf as a sub chart #860 in Additional Resources

Related

…chart

Since v0.1.11 (PR vllm-project#860), monitoring (kube-prometheus-stack, prometheus-adapter)
is available as an optional sub-chart dependency. The separate observability
install script is no longer needed.

Changes:
- Replace 'cd observability && bash install.sh' with values.yaml configuration
- Update Prometheus service addresses to match sub-chart naming
- Add note about using existing external Prometheus stacks
- Update version requirement to v0.1.11+
- Update cleanup section to reflect new approach

Signed-off-by: Ahmad Salah <a.salah@sprinteins.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the KEDA autoscaling tutorial to use the integrated monitoring stack (via kube-prometheus-stack and prometheus-adapter sub-charts) introduced in v0.1.11 of the Helm chart. The review feedback highlights a premature verification step in Step 1 before the stack is actually deployed, recommends replacing the placeholders with the concrete release name 'vllm' to make configurations copy-pasteable, and suggests disabling the redundant prometheus-adapter since KEDA queries Prometheus directly.

Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
Comment thread docs/source/use_cases/autoscaling-keda.rst Outdated
- Remove premature verification block from Step 1 (Prometheus is not
  deployed until helm install in Step 2)
- Replace <release-name> placeholder with 'vllm' for copy-paste-able examples
- Remove prometheus-adapter from examples (not required for KEDA, which
  queries Prometheus directly via its built-in scaler)
- Add note explaining when prometheus-adapter is actually needed

Signed-off-by: Ahmad Salah <a.salah@sprinteins.com>

@ruizhang0101 ruizhang0101 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ruizhang0101 ruizhang0101 merged commit 9b78da7 into vllm-project:main Jun 19, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants