-2. Set the `OPENAI_API_KEY` environment variable:
+3. Set the `OPENAI_API_KEY` environment variable:
```bash
export OPENAI_API_KEY="your-api-key-here"
```
-3. Install the kagent Helm chart:
+4. Install the kagent Helm chart:
```bash
helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
@@ -78,13 +80,13 @@ Another way to install kagent is using Helm.
-2. Set the `ANTHROPIC_API_KEY` environment variable:
+3. Set the `ANTHROPIC_API_KEY` environment variable:
```bash
export ANTHROPIC_API_KEY="your-api-key-here"
```
-3. Install the kagent Helm chart:
+4. Install the kagent Helm chart:
```bash
helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
@@ -95,13 +97,13 @@ Another way to install kagent is using Helm.
-2. Set the `OPENAI_API_KEY` environment variable:
+3. Set the `OPENAI_API_KEY` environment variable:
```bash
export OPENAI_API_KEY="your-api-key-here"
```
-3. Install the kagent Helm chart:
+4. Install the kagent Helm chart:
```bash
helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
@@ -113,13 +115,13 @@ Another way to install kagent is using Helm.
-2. Set the `GEMINI_API_KEY` environment variable:
+3. Set the `GEMINI_API_KEY` environment variable:
```bash
export GEMINI_API_KEY="your-api-key-here"
```
-3. Install the kagent Helm chart:
+4. Install the kagent Helm chart:
```bash
helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
@@ -131,7 +133,7 @@ Another way to install kagent is using Helm.
-2. Install the kagent Helm chart:
+3. Install the kagent Helm chart:
```bash
helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
diff --git a/src/app/docs/kagent/resources/release-notes/page.mdx b/src/app/docs/kagent/resources/release-notes/page.mdx
index 9a8cbbbf..85a70868 100644
--- a/src/app/docs/kagent/resources/release-notes/page.mdx
+++ b/src/app/docs/kagent/resources/release-notes/page.mdx
@@ -16,12 +16,16 @@ export const metadata = {
The kagent documentation shows information only for the latest release. If you run an older version, review the release notes to understand the main changes from version to version.
+For more details on the changes between versions, review the [kagent GitHub releases](https://github.com/kagent-dev/kagent/releases).
+
# v0.7
Review the main changes from kagent version 0.6 to v0.7, then continue reading for more detailed information.
* kmcp is installed by default when you install kagent
-* New! Develop agents locally without a Kubernetes cluster
+* New feature to develop agents locally without a Kubernetes cluster
+* New `kgateway.dev/discovery` label
+* Installation profiles
## kmcp installed by default
@@ -57,6 +61,20 @@ Develop and test agents locally on your machine without needing a Kubernetes clu
For more information, see the [local development](/docs/kagent/getting-started/local-development) guide.
+## Discovery label
+
+Now, you can add a discovery label to MCPServer kmcp resources. By default, discovery is enabled.
+
+If you plan to use your kmcp resources later with kagent and agentgateway, add the `kagent.dev/discovery=disabled` label to your MCPServer resource. Then, kagent does not automatically discover MCP servers. This way, you can have agentgateway in front of your kmcp servers so that the agent-tool traffic is routed correctly through agentgateway.
+
+## Installation profiles
+
+By default, kagent installs a `demo` profile with agents and MCP tools preloaded for you. If you don't want these default agents, you can disable them with the `minimal` profile.
+
+For the CLI: `kagent install --profile minimal`
+
+For Helm installations: Individually disable the default agents with Helm values or `--set` flags, such as `--set agents.argo-rollouts-agent.enabled=false`. You can also use Helm to update the resource limits and requests for each agent.
+
# v0.6
Review the main changes from kagent version 0.5 to v0.6, then continue reading for more detailed information.
diff --git a/src/app/docs/kmcp/deploy/server/page.mdx b/src/app/docs/kmcp/deploy/server/page.mdx
index ca2db935..a31a0076 100644
--- a/src/app/docs/kmcp/deploy/server/page.mdx
+++ b/src/app/docs/kmcp/deploy/server/page.mdx
@@ -99,7 +99,9 @@ The following example assumes that you created a [FastMCP](/docs/kmcp/develop/fa
kmcp build --project-dir my-mcp-server -t my-mcp-server:latest --kind-load-cluster kind
```
-2. Deploy your MCP server. Choose between the kmcp CLI or manually creating an MCPServer resource.
+2. Deploy your MCP server. Choose between the kmcp CLI or manually creating an MCPServer resource.
+
+ > **Note**: Planning to use your kmcp resources later with kagent and agentgateway? Add the `kagent.dev/discovery=disabled` label to your MCPServer resource. Then, kagent does not automatically discover MCP servers. This way, you can have agentgateway in front of your kmcp servers so that the agent-tool traffic is routed correctly through agentgateway.