[github-actions]

kagent-dev/kagent#3334 — [Helm] Use full DNS name for kagent tools MCP server

Docs versions: 1.x (first shipped in v1.0.0-rc1)

What changes for users: On clusters that use a DNS domain other than cluster.local, the kagent chart builds the bundled kagent-tool-server RemoteMCPServer URL with .svc.<global.clusterDomain>. Set global.clusterDomain during install so agents can reach built-in tools through the cluster's DNS suffix.

What the docs now say: The Install kagent page now shows when to set global.clusterDomain in the values file that kagent install passes to the chart, and names the generated kagent-tool-server URL as the reason.

Not verified: No cluster; the configuration is unrun.

How kagent-3334 was drafted, and what was not verified

• Code PR: [Helm] Use full DNS name for kagent tools MCP server kagent#3334
• Code issue: none linked
• Product: kagent (upstream) → kagent-dev/website
• Docs version: 1.x, first shipped in v1.0.0-rc1
• Category: new-feature / pr

Plan, and what changed it

• Planned: Add prose for global.clusterDomain to one of the code-path candidate pages.
• Learned: installation.md owns the values file that reaches kagent install; operational-considerations.md is production tuning and does not own initial chart defaults.
• Did: Documented the custom cluster-domain case on docs-site/content/kagent/1.x/setup/installation.md.

Why a documentation change is necessary

The pull request changes the generated kagent-tool-server RemoteMCPServer URL from http://<service>.<namespace>:8084/mcp to http://<service>.<namespace>.svc.<global.clusterDomain>:8084/mcp. The generated Helm reference already lists global.clusterDomain, but it is regenerated and cannot carry the usage guidance. The installation guide already creates the values file that feeds the kagent chart, so it is the page where a reader needs to learn when to set the field.

What changed on disk

docs-site/content/kagent/1.x/setup/installation.md — Added the optional global.clusterDomain values snippet for clusters with a non-default DNS domain.

How to verify this change

1. Install kagent with a values file that sets a non-default cluster domain.

   cat > kagent-values.yaml <<EOF
   global:
     clusterDomain: corp.example
   config:
     server:
       grpcReflection: true
   EOF
   
   cat > kagent-config.yaml <<EOF
   install:
     kagent:
       valuesFiles: [kagent-values.yaml]
   EOF
   
   kagent --config kagent-config.yaml install --namespace kagent

2. Read the generated RemoteMCPServer URL.

   kubectl get remotemcpserver kagent-tool-server -n kagent -o jsonpath='{.spec.url}'

   The value includes .svc.corp.example:8084/mcp.
3. Check that the controller accepts the generated server.

   kubectl get remotemcpserver kagent-tool-server -n kagent -o jsonpath='{.status.conditions[?(@.type=="Accepted")].status}'

   The value is True.

Proposed release note

No proposed-release-note.md: markers.notes_placeable is false for this product. Suggested text: The kagent chart now uses global.clusterDomain when it creates the bundled kagent-tool-server RemoteMCPServer URL, so clusters with a DNS domain other than cluster.local can install kagent with the correct in-cluster service address.

What was not verified

• The configuration was not applied to a cluster, so every command in this diff is unrun.
• Internal links are unchecked because Hugo was not run.
• The later follow-up fix helm full DNS name tests kagent#3336 was represented only as a test-file summary in the dossier, with no hunk contents to apply to the page.

How the pages were chosen (triage report)

Feature clusters

Kept apart on purpose. Merging wrongly produces a guide that documents two things and explains neither, so these are reported for a person to merge rather than grouped automatically:

• [Helm] Use full DNS name for kagent tools MCP server kagent#3334 and an internal repository#630 both have docs-site/content/kagent/1.x/setup/installation.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there

New configuration: no page mentions it yet

kagent-dev/kagent#3334 — [Helm] Use full DNS name for kagent tools MCP server

• Product: kagent (upstream) → kagent-dev/website
• Docs version: 1.x
• Summary (read from the body): We should follow our own docs:
• Not tested: no cluster was available, so every command in this diff is unrun

Draft branch: pr-tracker-draft-kagent-3334

[Rachael-Graham]

Folded into #672.