Scaling to Zero
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Hello,
Firstly I appreciate the great effort you people taking in improving the mcp server deployment in K8s world.
I have been testing this tool for quite some time. It looks promising to make our k8s suitable for the mcp server deployment.
One thing stuck in my head is few mcp servers are rarely used and might be used once in a while during that situation I just want to scale the deployment to zero so, that I can avoid some idle cost. I am okay if the initial request fails because I'll implement retry strategy.
I want to check is there any solution planned to handle these types of requirements from tool hive side or does it need any external tool like native/openfaas to support this.
It would be really helpful if some pointers or guidance is provided.
Thank you !
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
No files, tests, or entry points are identified. Start by reviewing how ToolHive manages MCP server deployments in Kubernetes, then determine whether scaling a deployment to zero and handling the first request is supported natively or requires an external tool such as OpenFaaS. Done means documenting the supported approach and its retry implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100