Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs-site/content/kagent/0.x/concepts/agent-substrate.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/).
2 changes: 1 addition & 1 deletion docs-site/content/kagent/0.x/supported-providers/gemini.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion docs-site/content/kagent/latest/operations/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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=<your_api_key>
```
Expand Down
2 changes: 1 addition & 1 deletion docs-site/content/kagent/main/operations/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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=<your_api_key>
```
Expand Down
Loading