From 89d19860b43890cba2a26c8b21a21dc43d70735f Mon Sep 17 00:00:00 2001 From: Kristin Brown Date: Mon, 16 Nov 2026 07:41:52 -0500 Subject: [PATCH] Link fixes Signed-off-by: Kristin Brown --- docs-site/content/kagent/0.x/concepts/agent-substrate.md | 2 +- docs-site/content/kagent/0.x/supported-providers/gemini.md | 2 +- docs-site/content/kagent/latest/operations/upgrade.md | 2 +- docs-site/content/kagent/latest/setup/model-providers/gemini.md | 2 +- docs-site/content/kagent/main/operations/upgrade.md | 2 +- docs-site/content/kagent/main/setup/model-providers/gemini.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs-site/content/kagent/0.x/concepts/agent-substrate.md b/docs-site/content/kagent/0.x/concepts/agent-substrate.md index f7347be8..2c89dc2f 100644 --- a/docs-site/content/kagent/0.x/concepts/agent-substrate.md +++ b/docs-site/content/kagent/0.x/concepts/agent-substrate.md @@ -75,4 +75,4 @@ See the [API reference]({{< link path="resources/api-ref" >}}) for the full `Age ## Learn more - [Run a declarative agent on Agent Substrate]({{< link path="examples/agent-substrate" >}}) — end-to-end walkthrough on a kind cluster. -- For a deeper dive into the runtime internals, see the [Agent Substrate documentation](https://learn.agentsubstrate.dev/). +- For a deeper dive into the runtime internals, see the [Agent Substrate documentation](https://ate.dev/). diff --git a/docs-site/content/kagent/0.x/supported-providers/gemini.md b/docs-site/content/kagent/0.x/supported-providers/gemini.md index f535509c..41bf9791 100644 --- a/docs-site/content/kagent/0.x/supported-providers/gemini.md +++ b/docs-site/content/kagent/0.x/supported-providers/gemini.md @@ -13,7 +13,7 @@ Make sure that your Google Cloud account has a project with the Gemini API enabl ## Configuring Gemini -1. Get your API key from [Google AI Studio](https://ai.google.dev/). +1. Get your API key from [Google AI Studio](https://aistudio.google.com/welcome). 2. Create a Kubernetes Secret that stores the API key. diff --git a/docs-site/content/kagent/latest/operations/upgrade.md b/docs-site/content/kagent/latest/operations/upgrade.md index 7b47d28c..795f90be 100644 --- a/docs-site/content/kagent/latest/operations/upgrade.md +++ b/docs-site/content/kagent/latest/operations/upgrade.md @@ -26,7 +26,7 @@ Complete every step in this section before you change any release. The steps mak * The `substrate`, `substrate-atelet`, and `substrate-crds` releases are in the `ate-system` namespace. * The `substrate-podcert` release is in the `podcertificate-controller-system` namespace. - If the output does not list a `substrate-atelet` release, the `substrate` release still runs `atelet`, and the rest of this guide does not apply to that installation. First, back up the PostgreSQL database and record its schema version, as this section describes. Then follow the steps in [Upgrading from v1.0.0-rc2](https://github.com/kagent-dev/kagent/releases/tag/v1.0.0-rc3#upgrading-from-v100-rc2) instead of the remaining steps of this guide. Those steps move `atelet` to its own release without deleting the `atelet` DaemonSet, turn on the `GoldenEgressPolicy` gate, and upgrade kagent. To confirm the result, see [Verify the upgrade](#verify-the-upgrade). + If the output does not list a `substrate-atelet` release, the `substrate` release still runs `atelet`, and the rest of this guide does not apply to that installation. First, back up the PostgreSQL database and record its schema version, as this section describes. Then follow the steps in [Upgrading from v1.0.0-rc2](https://github.com/kagent-dev/kagent/releases/tag/v1.0.0-rc3) instead of the remaining steps of this guide. Those steps move `atelet` to its own release without deleting the `atelet` DaemonSet, turn on the `GoldenEgressPolicy` gate, and upgrade kagent. To confirm the result, see [Verify the upgrade](#verify-the-upgrade). 4. Back up the PostgreSQL database that kagent and Agent Substrate share. The upgrade keeps your data. However, the kagent controller and the Agent Substrate API server change the database schema when they start on the new version. To return to the previous version, you must restore the backup or roll the schema back. ```bash diff --git a/docs-site/content/kagent/latest/setup/model-providers/gemini.md b/docs-site/content/kagent/latest/setup/model-providers/gemini.md index d35a3ea8..0db9ebd8 100644 --- a/docs-site/content/kagent/latest/setup/model-providers/gemini.md +++ b/docs-site/content/kagent/latest/setup/model-providers/gemini.md @@ -13,7 +13,7 @@ Make sure that your Google Cloud account has a project with the Gemini API enabl ## Create the ModelConfig -1. Save your [Google AI Studio](https://ai.google.dev/) API key as an environment variable. +1. Save your [Google AI Studio](https://aistudio.google.com/welcome) API key as an environment variable. ```bash export GOOGLE_API_KEY= ``` diff --git a/docs-site/content/kagent/main/operations/upgrade.md b/docs-site/content/kagent/main/operations/upgrade.md index 7b47d28c..795f90be 100644 --- a/docs-site/content/kagent/main/operations/upgrade.md +++ b/docs-site/content/kagent/main/operations/upgrade.md @@ -26,7 +26,7 @@ Complete every step in this section before you change any release. The steps mak * The `substrate`, `substrate-atelet`, and `substrate-crds` releases are in the `ate-system` namespace. * The `substrate-podcert` release is in the `podcertificate-controller-system` namespace. - If the output does not list a `substrate-atelet` release, the `substrate` release still runs `atelet`, and the rest of this guide does not apply to that installation. First, back up the PostgreSQL database and record its schema version, as this section describes. Then follow the steps in [Upgrading from v1.0.0-rc2](https://github.com/kagent-dev/kagent/releases/tag/v1.0.0-rc3#upgrading-from-v100-rc2) instead of the remaining steps of this guide. Those steps move `atelet` to its own release without deleting the `atelet` DaemonSet, turn on the `GoldenEgressPolicy` gate, and upgrade kagent. To confirm the result, see [Verify the upgrade](#verify-the-upgrade). + If the output does not list a `substrate-atelet` release, the `substrate` release still runs `atelet`, and the rest of this guide does not apply to that installation. First, back up the PostgreSQL database and record its schema version, as this section describes. Then follow the steps in [Upgrading from v1.0.0-rc2](https://github.com/kagent-dev/kagent/releases/tag/v1.0.0-rc3) instead of the remaining steps of this guide. Those steps move `atelet` to its own release without deleting the `atelet` DaemonSet, turn on the `GoldenEgressPolicy` gate, and upgrade kagent. To confirm the result, see [Verify the upgrade](#verify-the-upgrade). 4. Back up the PostgreSQL database that kagent and Agent Substrate share. The upgrade keeps your data. However, the kagent controller and the Agent Substrate API server change the database schema when they start on the new version. To return to the previous version, you must restore the backup or roll the schema back. ```bash diff --git a/docs-site/content/kagent/main/setup/model-providers/gemini.md b/docs-site/content/kagent/main/setup/model-providers/gemini.md index d35a3ea8..0db9ebd8 100644 --- a/docs-site/content/kagent/main/setup/model-providers/gemini.md +++ b/docs-site/content/kagent/main/setup/model-providers/gemini.md @@ -13,7 +13,7 @@ Make sure that your Google Cloud account has a project with the Gemini API enabl ## Create the ModelConfig -1. Save your [Google AI Studio](https://ai.google.dev/) API key as an environment variable. +1. Save your [Google AI Studio](https://aistudio.google.com/welcome) API key as an environment variable. ```bash export GOOGLE_API_KEY= ```