Helm

Install standalone agentgateway as a Kubernetes Deployment with the standalone Helm chart.

Use the standalone Helm chart when you want the standalone agentgateway model, but you want Kubernetes to run and expose the process for you. The chart runs the same binary and reads the same configuration file that the binary and Docker installations use. You supply that file through Helm values, and the chart renders it into a ConfigMap that the proxy reads at startup.

Tip

This chart installs agentgateway as a single, unmanaged Kubernetes Deployment. You manage agentgateway config by upgrading the Helm values, and optionally by adding a PostgreSQL database so that you can edit the config in the UI. If you want a managed Kubernetes solution that includes a control plane and Gateway API resources, see Kubernetes control plane.

Before you begin

Create or use an existing Kubernetes cluster.
Install the following command-line tools.
- kubectl, the Kubernetes command line tool.
- helm, the Kubernetes package manager.

Install

Install the standalone Helm chart.

helm upgrade -i agentgateway-standalone \
  oci://cr.agentgateway.dev/charts/agentgateway-standalone \
  --namespace agentgateway-system \
  --create-namespace \
  --version 0.0.0-latest-dev

To install with a different name and in a different namespace, set both the Helm release namespace and namespaceOverride setting.

The following example installs an agw Helm release in the agw namespace.

helm upgrade -i agw \
  oci://cr.agentgateway.dev/charts/agentgateway-standalone \
  --namespace agw \
  --create-namespace \
  --version 0.0.0-latest-dev \
  --set namespaceOverride=agw

What the chart installs

The chart creates the following resources. Each resource is named after the Helm release, which is agentgateway-standalone in these examples.

Resource	Name	Purpose
Deployment	`agentgateway-standalone`	Runs the agentgateway proxy.
ConfigMap	`agentgateway-standalone-config`	Holds the rendered `config.yaml`, mounted read-only at `/config`.
Service	`agentgateway-standalone`	Exposes the gateway listener. Type `LoadBalancer` and port `80` to container port `4000` by default.
ServiceAccount	`agentgateway-standalone`	Identity for the proxy pod.

If you installed with a different release name or namespace, such as with the Unique name and namespace tab, adjust the resource names and the -n values in the commands throughout this documentation accordingly.

What the chart does not install

Keep in mind that the Helm chart installation does not include the following features:

No PersistentVolumeClaim for persistent storage.
No Service for the admin port. Instead, you can reach the admin interface by port-forwarding the agentgateway-standalone Deployment.
No writeable UI by default. To make the UI writable, see Configuration storage.
No database for features such as LLM analytics, LLM logs, API key budgets, and hybrid storage. To add a database, see Database.

Also keep in mind that this standalone Kubernetes Deployment via Helm does not include the features of agentgateway for Kubernetes, such as a control plane, agentgateway custom resources, or additional services such as rate limiting, external auth, and WAF.

Verify the installation

Verify that the agentgateway pod is running.

kubectl get pods -n agentgateway-system \
  -l app.kubernetes.io/name=agentgateway-standalone

Example output:

NAME                                       READY   STATUS    RESTARTS   AGE
agentgateway-standalone-6d5dc56bdb-792pt   1/1     Running   0          30s

Review the configuration that the chart rendered into the ConfigMap.

kubectl get configmap agentgateway-standalone-config \
  -n agentgateway-system -o jsonpath='{.data.config\.yaml}'

Example output: Note that storage is nested in agentgateway’s own top-level config section, which the chart manages for you based on the mode value.

config:
  storage:
    mode: file
gateways:
  default:
    port: 4000
llm:
  models: []
mcp:
  targets: []
ui: {}

Open the UI

For quick access to the UI, port-forward the agentgateway-standalone Deployment and open the /ui path.

Port-forward the admin interface.

kubectl port-forward -n agentgateway-system \
  deploy/agentgateway-standalone 15000:15000

In your browser, open the /ui path: http://localhost:15000/ui

A port-forward is a quick way to look at the UI on a cluster. To give the UI its own gateway so that you can reach it without one, secure it with OIDC, and expose it on your own hostname, see UI.

Common Helm values

Review the following table to understand this configuration. For more information, see the Helm reference docs.

Value	Use
`replicaCount`	Run more than one proxy pod.
`monitoring.enabled`	Create a PodMonitor and expose the metrics port for Prometheus Operator.
`extraEnv`, `extraVolumes`, `extraVolumeMounts`, `extraContainers`	Add environment variables, mount secrets, or run sidecars.
`imagePullSecrets`	Pull the proxy image from a private registry.
`image.registry`, `image.repository`, `image.tag`	Pull the proxy image from another registry, such as an internal mirror.

Uninstall

Uninstall the Helm release.

helm uninstall agentgateway-standalone -n agentgateway-system

Remove the namespace or any PostgreSQL database that you created.
```
kubectl delete namespace agentgateway-system
```

Next steps

Set up the UI to give the UI its own gateway and secure it with OIDC.
Set up a database so that the Analytics and Logs pages have data to show.
Choose where configuration is stored so that the UI can save your changes.
Update your configuration by upgrading your Helm values.
Upgrade agentgateway to a new chart version.

Docker Kubernetes control plane

Was this page helpful?