kubeflow / kubeflow/docs-agent
feat: Add Scale-to-Zero configuration to KServe InferenceService
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 42
- Forks
- 111
- Avg merge
- 6d 23m
- Merged PRs (30d)
- 2
Description
Problem
The current manifests/inference-service.yaml has no autoscaling configuration. The InferenceService will keep GPU nodes running continuously even when idle, which is costly and inefficient for the bursty, on-demand query patterns of a documentation assistant.
Proposed Solution
Add Scale-to-Zero using KServe's Knative-based autoscaling annotations:
- Set
minReplicas: 0to allow full scale-down when idle - Configure
scaleTargetandscaleMetric(e.g. concurrency-based) - Document cold-start latency tradeoff in README
- Add optional KEDA-based scaling config as an alternative for
clusters without Knative
Why This Matters
Scale-to-Zero for bursty workloads is explicitly listed as a key deliverable in the GSoC project scope for this repo. This change also makes the reference architecture more cost-practical for community members deploying on OCI or other clouds.
References
- KServe autoscaling docs: https://kserve.github.io/website/latest/modelserving/autoscaling/autoscaling/
- GSoC proposal: Agentic RAG on Kubeflow
I'd like to work on this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with manifests/inference-service.yaml and the referenced KServe autoscaling documentation to identify the repository's InferenceService configuration. Update the manifest for minReplicas, scaleTarget, and scaleMetric, document cold-start tradeoffs in README, and determine whether the optional KEDA alternative is in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100