-
Couldn't load subscription status.
- Fork 83
docs: explain MCP deployments in k8s #4757
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
Conversation
Signed-off-by: Grant Linville <[email protected]>
Co-authored-by: Donnie Adams <[email protected]>
|
|
||
| ## Namespace | ||
|
|
||
| Obot will deploy MCP servers into the namespace `{helm-release-name}-mcp`. So if your Helm release name is `obot`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth mentioning that this is configurable - it will do this by default but it can be overridden by setting a value for mcpNamespace.name
|
|
||
| In order to set up Deployments, Services, and Secrets, Obot needs a ServiceAccount, Role, and RoleBinding | ||
| that give it permissions to do so in the namespace. All of this is included in the Helm chart. | ||
| These are the permissions included on its Role: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of showing this directly in the docs, it might make more sense to just link to the chart. less chance of it getting out of date that way
Signed-off-by: Grant Linville <[email protected]>
Signed-off-by: Grant Linville <[email protected]>
for #4241