Skip to content

Conversation

@g-linville
Copy link
Member

for #4241

@g-linville g-linville requested a review from thedadams October 24, 2025 18:23

## Namespace

Obot will deploy MCP servers into the namespace `{helm-release-name}-mcp`. So if your Helm release name is `obot`,
Copy link
Contributor

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:
Copy link
Contributor

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

@g-linville g-linville requested a review from drpebcak October 24, 2025 22:57
Signed-off-by: Grant Linville <[email protected]>
Signed-off-by: Grant Linville <[email protected]>
@g-linville g-linville merged commit d58a016 into obot-platform:main Oct 27, 2025
4 checks passed
@g-linville g-linville deleted the k8s-mcp-docs branch October 27, 2025 13:05
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.

3 participants