For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.
Install agentgateway
Install the agentgateway control plane in your Kubernetes cluster.
Install the Solo Enterprise for agentgateway control plane and get agentgateway running in your cluster. Agentgateway is an open source, AI-first data plane that provides connectivity for agents, MCP tools, LLMs, and inferences in any environment. In Kubernetes environments, you can use Solo Enterprise for agentgateway as the control plane to quickly spin up and manage the lifecycle of agentgateway proxies. The control plane translates Kubernetes Gateway API and agentgateway’s Kubernetes custom resources such as EnterpriseAgentgatewayPolicy and EnterpriseAgentgatewayBackend into proxy configuration for the data plane.
Before you begin
These steps assume that you have a Kubernetes cluster, kubectl, and helm already set up. For quick testing, you can use Kind.
kind create clusterInstall
The following steps get you started with a basic installation. For detailed instructions, see the installation guides.
Set your Solo Enterprise for agentgateway license key as an environment variable. If you do not have one, contact an account representative.
export AGENTGATEWAY_LICENSE_KEY=<agentgateway-license-key>Deploy the Kubernetes Gateway API CRDs.
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.6.1/standard-install.yamlDeploy the Solo Enterprise for agentgateway CRDs by using Helm. The following command uses version 2026.10.2.
helm upgrade -i enterprise-agentgateway-crds oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway-crds \ --create-namespace \ --namespace agentgateway-system \ --version v2026.10.2Install Solo Enterprise for agentgateway by using Helm.
helm upgrade -i enterprise-agentgateway oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway \ -n agentgateway-system \ --version v2026.10.2 \ --set-string licensing.licenseKey=${AGENTGATEWAY_LICENSE_KEY}Make sure that the
enterprise-agentgatewaycontrol plane is running.kubectl get pods -n agentgateway-systemExample output:
NAME READY STATUS RESTARTS AGE enterprise-agentgateway-5495d98459-46dpk 1/1 Running 0 19s
Note
The data plane pods, including the agentgateway-proxy, ext-auth-service, rate-limiter, and ext-cache are created only after you deploy a Gateway resource in your environment.
Good job! You now have the Solo Enterprise for agentgateway control plane running in your cluster.
Set up an agentgateway proxy
Create a Gateway that uses the
enterprise-agentgatewayGatewayClass. The following example sets up a Gateway that uses the default agentgateway proxy template.kubectl apply -f- <<EOF apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: agentgateway-proxy namespace: agentgateway-system spec: gatewayClassName: enterprise-agentgateway listeners: - protocol: HTTP port: 80 name: http allowedRoutes: namespaces: from: All EOFNote
The generated service for a Gateway is of type
LoadBalancerby default. Depending on your load balancer implementation, each Gateway can consume an external IP address from the address pool of your cluster, so creating many Gateways can exhaust that pool. If a Gateway does not need to be reachable from outside the cluster, set the service type toClusterIPinstead. For more information, see Internal-only ClusterIP service.Verify that the agentgateway proxy is created.
- Gateway: Note that it might take a few minutes for an address to be assigned.
- Pod for
agentgateway-proxy: The pod has one container:agent-gateway.
kubectl get gateway agentgateway-proxy -n agentgateway-system kubectl get deployment agentgateway-proxy -n agentgateway-systemExample output:
NAME CLASS ADDRESS PROGRAMMED AGE agentgateway-proxy enterprise-agentgateway a1cff4bd974a34d8b882b2fa01d357f0-119963959.us-east-2.elb.amazonaws.com True 6m9s NAME READY UP-TO-DATE AVAILABLE AGE agentgateway-proxy 1/1 1 1 6m11sGet the address to access the agentgateway proxy. The steps depend on how your cluster exposes the proxy service.
Tip
Kind cluster? Kind does not support
LoadBalancerservices by default. To use this option with a Kind cluster, install and runcloud-provider-kind.Verify that the external IP has been created and is not
pending.kubectl get svc -n agentgateway-system agentgateway-proxyExample output:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE agentgateway-proxy LoadBalancer 172.20.200.127 172.18.255.200 80:30752/TCP 7m6sSave the external address of the agentgateway proxy in an environment variable.
export INGRESS_GW_ADDRESS=$(kubectl get svc -n agentgateway-system agentgateway-proxy -o jsonpath="{.status.loadBalancer.ingress[0]['hostname','ip']}") echo $INGRESS_GW_ADDRESSFor local testing, port-forward to the agentgateway proxy. Use this option if your cluster does not assign an external IP to
LoadBalancerservices, such as a default Kind cluster.kubectl port-forward deployment/agentgateway-proxy -n agentgateway-system 8080:80
Next steps
Choose a quick start to route traffic with agentgateway:
Cleanup
No longer need Solo Enterprise for agentgateway? Uninstall with the following command:
helm uninstall enterprise-agentgateway enterprise-agentgateway-crds -n agentgateway-system