Skip to content

adds proposal for toolhive k8s deployment architecture #1497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ChrisJBurns
Copy link
Collaborator

Wanted to get some early thoughts on this.

@ChrisJBurns to refine technical details if needed

Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
@ChrisJBurns ChrisJBurns marked this pull request as draft August 19, 2025 19:09
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
@RoddieKieley
Copy link
Contributor

Initial thoughts. This makes a lot of sense to me @ChrisJBurns. The operator should indeed be taking responsibility for both the deployment and statefulset creation, and then also their association with various kubernetes services and other resources such that their reconciliation and reclamation can happen cleanly.

I also like the idea of having the proxy still being able to request an mcp server replica + or - depending on the load it is experiencing, and while the operator has the big picture the proxy will have the data to determine the need most directly.

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