Build Kubernetes manifest to deploy server in a cluster

[nimishamehta5]

We should have a simple Kubernetes manifest to pull the latest Docker image and deploy the server as a standalone deployment in its own namespace.

[nimishamehta5]

@JAORMX @ChrisJBurns, I was looking into this, but realized that if we set up RBAC for the Kubernetes manifest, the role won't have access to interact with custom resources unless rules for that are explicitly added in the RBAC config.
This works locally because the local Kubeconfig has a wider set of permissions.
Any thoughts on how to handle this?

As far as I can tell, thv uses the user's local kubeconfig by mounting it into the tool hive container

[ChrisJBurns]

Hey @nimishamehta5

I'm looking at RBAC currently for ToolHive Operator, mainly to allow for multi-namespace. What will happen is that you will be able to deploy mkp into the cluster using the Operator and it will setup the permissions in order to run certain commands. There will be further work in order to specify additional RBAC permissions that you want your MCP ServiceAccount to be able to perform.

[nimishamehta5]

@ChrisJBurns Sounds good, is the operator going to be in a separate project (not the mkp repo)?

[ChrisJBurns]

@nimishamehta5

Yep, it is it's own thing https://github.com/stacklok/toolhive/tree/main/cmd/thv-operator and https://github.com/stacklok/toolhive/tree/main/deploy/charts. I've also raised stacklok/toolhive#654 for the use case of needing more custom RBAC rules for MCP servers.