Blog: Install Agent Substrate on Any Kubernetes Cluster by sebbycorp · Pull Request #722 · kagent-dev/website

sebbycorp · 2026-11-11T16:26:00Z

New blog post by Michael Levan on the universal kubectl-ate installer, which sets up Agent Substrate on any Kubernetes cluster (Kind, Minikube, AKS, EKS, GKE) without cloud-specific workarounds like setting a placeholder PROJECT_ID.

src/blogContent/install-agent-substrate-any-cluster.mdx: the post
src/app/blog/page.tsx: blog index entry
public/images/blog/install-agent-substrate-any-cluster/: installer GIF, options and confirm screenshots, ate-system pods

Copy edits from the draft: fixed the PATH export ($HOME/$PATH were missing the $), noted the download uses the darwin-arm64 build, added kubectl get pods -n ate-system before the final screenshot, and tightened some wording.

🤖 Generated with Claude Code

Michael Levan's post on the universal kubectl-ate installer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Sebastian Maniak <sebastian@maniak.io>

github-actions · 2026-11-11T16:29:19Z

Docs preview

Link	Points at
Branch preview	The newest push to this branch. Updates in place.
Commit preview	`a539ce5` only. Frozen.

Both are uploaded Worker versions and serve no production traffic.

Nadine2016 · 2026-11-11T22:19:45Z

+
+To follow along with this blog post in a hands-on fashion, you need:
+
+1. A Kubernetes cluster running v1.37 or above. It can be any cluster, from a Kind or Minikube cluster to an AKS, EKS, or GKE cluster.


remove the numbering since there is only one condition. I would also just make it one combined paragraph

Nadine2016 · 2026-11-11T22:22:01Z

+
+1. Download the `kubectl-ate` binary, which is how you interact with Agent Substrate on the CLI. This example pulls the macOS (Apple silicon) build; pick the pattern that matches your OS and architecture.
+
+```bash


the commands need to be indented to align with the steps

Nadine2016 · 2026-11-12T04:04:39Z

+
+## What Does the Installer Entail?
+
+When you run the installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.


the same as if you'd installed it on GKE or Kind.

this phrase sounds like as if I manually installed it on GKE or Kind. but I think we want to say whether you install on GKE or kind?

Nadine2016 · 2026-11-12T04:05:14Z

+
+![The kubectl-ate installer running against a cluster: preflight checks, component installation, and post-install verification.](/images/blog/install-agent-substrate-any-cluster/installer-run.gif)
+
+The installer:


Suggested change

The installer:

The installer completes the following steps:

Nadine2016 · 2026-11-12T04:05:35Z

+The installer:
+
+1. Checks that the cluster has what it needs to run as expected (for example, the PodCertificate API).
+2. Installs all of the necessary components: CRDs, the cert controller, Postgres, and all of the Substrate components.


Suggested change

2. Installs all of the necessary components: CRDs, the cert controller, Postgres, and all of the Substrate components.

2. Installs all of the necessary components, including the CRDs, the cert controller, Postgres, and all of the Substrate components.

Nadine2016 · 2026-11-12T04:10:36Z

+
+## Why Is a Universal Installer Needed?
+
+"Where can this run?"


An alternative to your text, because there are a lot of questions after another. and the point of using an universal installer did not really come across to me this way.

Suggested change

"Where can this run?"

Portability is one of the first things teams weigh when they adopt a platform. They want to know whether it runs outside a single cloud, whether their data can leave, and whether a workload can move from one environment to another.

A tool that only runs in one cloud locks you in the moment your needs change, whether the trigger is billing, a better deal, or more experience with another provider. A universal installer removes that risk. Teams reuse the same setup everywhere instead of building a one-off "snowflake" for each environment.

Nadine2016 · 2026-11-12T04:11:04Z

+
+## What Does the Installer Entail?
+
+When you run the installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.


Suggested change

When you run the installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.

When you run the Agent Substrate installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.

Nadine2016 · 2026-11-12T04:14:31Z

+
+## How to Use the Installer
+
+To get past those "hacky" workarounds, use the universal installer in the [kagent Agent Substrate fork](https://github.com/kagent-dev/substrate).


earlier we say that the installer requires a project ID env, even if it is not used. but here we say the installer gets you past the workarounds. not sure what is right?

Blog: install Agent Substrate on any Kubernetes cluster

a539ce5

Michael Levan's post on the universal kubectl-ate installer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Sebastian Maniak <sebastian@maniak.io>

sebbycorp force-pushed the blog/install-agent-substrate-any-cluster branch from cf83235 to a539ce5 Compare November 11, 2026 16:27

sebbycorp requested review from EItanya, artberger and christian-posta November 11, 2026 17:18

Nadine2016 reviewed Nov 11, 2026

View reviewed changes

Nadine2016 reviewed Nov 12, 2026

View reviewed changes

Navigation Menu

Repository navigation

Blog: Install Agent Substrate on Any Kubernetes Cluster - #722

Blog: Install Agent Substrate on Any Kubernetes Cluster#722
sebbycorp wants to merge 1 commit into
mainfrom
blog/install-agent-substrate-any-cluster

sebbycorp commented Nov 11, 2026

Uh oh!

github-actions Bot commented Nov 11, 2026

Uh oh!

Nadine2016 Nov 11, 2026

Uh oh!

Nadine2016 Nov 11, 2026

Uh oh!

Nadine2016 Nov 12, 2026

Uh oh!

Nadine2016 Nov 12, 2026

Uh oh!

Nadine2016 Nov 12, 2026

Uh oh!

Nadine2016 Nov 12, 2026

Uh oh!

Nadine2016 Nov 12, 2026

Uh oh!

Nadine2016 Nov 12, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		To follow along with this blog post in a hands-on fashion, you need:

		1. A Kubernetes cluster running v1.37 or above. It can be any cluster, from a Kind or Minikube cluster to an AKS, EKS, or GKE cluster.


		1. Download the `kubectl-ate` binary, which is how you interact with Agent Substrate on the CLI. This example pulls the macOS (Apple silicon) build; pick the pattern that matches your OS and architecture.

		```bash


		## What Does the Installer Entail?

		When you run the installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.


		![The kubectl-ate installer running against a cluster: preflight checks, component installation, and post-install verification.](/images/blog/install-agent-substrate-any-cluster/installer-run.gif)

		The installer:

	2. Installs all of the necessary components: CRDs, the cert controller, Postgres, and all of the Substrate components.
	2. Installs all of the necessary components, including the CRDs, the cert controller, Postgres, and all of the Substrate components.


		## Why Is a Universal Installer Needed?

		"Where can this run?"

-"Where can this run?"
+Portability is one of the first things teams weigh when they adopt a platform. They want to know whether it runs outside a single cloud, whether their data can leave, and whether a workload can move from one environment to another.
+A tool that only runs in one cloud locks you in the moment your needs change, whether the trigger is billing, a better deal, or more experience with another provider. A universal installer removes that risk. Teams reuse the same setup everywhere instead of building a one-off "snowflake" for each environment.

	When you run the installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.
	When you run the Agent Substrate installer, you get everything that comes with a standard Agent Substrate installation, the same as if you'd installed it on GKE or Kind.


		## How to Use the Installer

		To get past those "hacky" workarounds, use the universal installer in the [kagent Agent Substrate fork](https://github.com/kagent-dev/substrate).

Conversation

sebbycorp commented Nov 11, 2026

Uh oh!

github-actions Bot commented Nov 11, 2026

Docs preview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants