Skip to content

[Automated] Draft docs (kagent): [Helm] Use full DNS name for kagent tools MCP server #659

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.

Sign up for GitHub

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

Closed
github-actions wants to merge 1 commit into from
Closed

[Automated] Draft docs (kagent): [Helm] Use full DNS name for kagent tools MCP server #659

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs-site/content/kagent/1.x/setup/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,16 @@ The kagent CLI installs the CRDs, Agent Substrate, the Agent Substrate PodCertif
EOF
```

If your cluster uses a DNS domain other than `cluster.local`, add `global.clusterDomain` to the same file. The chart uses this value for runtime-facing service URLs. For example, agents use the `kagent-tool-server` RemoteMCPServer URL for built-in tools.

```yaml
global:
clusterDomain: corp.example
config:
server:
grpcReflection: true
```

2. Save a CLI configuration file that points the installer at those values. `kagent install` does not take Helm flags of its own, so chart values reach it through this file. A relative path in `valuesFiles` resolves against the configuration file's own directory.
```bash
cat > kagent-config.yaml <<EOF
Expand Down