Skip to content
Latest (currently 2026.10.2) has the newest features, bug fixes, and CVE patches of Solo Enterprise for agentgateway.

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Helm

Page as Markdown

Note

Red Hat OpenShift: The security context constraints that OpenShift enforces reject some of the default security settings on this page. Before you install, review the OpenShift guide, which lists the settings to change and the steps to skip.

In this installation guide, you install the Solo Enterprise for agentgateway control planeControl PlaneComponents that manage and distribute configuration and policies to the data plane. in a Kubernetes cluster by using Helm. Helm is a popular package manager for Kubernetes configuration files. This approach is flexible for adopting to your own command line, continuous delivery, or other workflows.

As part of the control plane installation, you enable the agentgateway data plane.

Before you begin

  1. Create or use an existing Kubernetes cluster.
  2. Install the following command-line tools.
    • kubectl, the Kubernetes command line tool. Download the kubectl version that is within one minor version of the Kubernetes clusters you plan to use.
    • helm, the Kubernetes package manager.

Install

Install the Solo Enterprise for agentgateway control plane by using Helm.

  1. 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>
  2. Install the custom resources of the Kubernetes Gateway API version 1.6.1.

    kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.6.1/standard-install.yaml

    CRDs in the experimental channel are required to use some experimental features in the Gateway API. Guides that require experimental CRDs note this requirement in their prerequisites.

    kubectl apply --server-side -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.6.1/experimental-install.yaml
    Example output:

    customresourcedefinition.apiextensions.k8s.io/gatewayclasses.gateway.networking.k8s.io created
    customresourcedefinition.apiextensions.k8s.io/gateways.gateway.networking.k8s.io created
    customresourcedefinition.apiextensions.k8s.io/httproutes.gateway.networking.k8s.io created
    customresourcedefinition.apiextensions.k8s.io/referencegrants.gateway.networking.k8s.io created
    customresourcedefinition.apiextensions.k8s.io/grpcroutes.gateway.networking.k8s.io created
    
  3. Apply the Solo Enterprise for agentgateway CRDs for the upgrade version by using Helm.

    1. Optional: To check the CRDs locally, download the CRDs to a helm directory.

      helm template --version v2026.10.2 enterprise-agentgateway-crds oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway-crds --output-dir ./helm
    2. Deploy the Solo Enterprise for agentgateway CRDs by using Helm. This command creates the agentgateway-system namespace and creates the Solo Enterprise for agentgateway CRDs in the cluster.

      helm upgrade -i --create-namespace \
        --namespace agentgateway-system \
        --version v2026.10.2 enterprise-agentgateway-crds oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway-crds 
  4. Install the Solo Enterprise for agentgateway Helm chart.

    1. Optional: Pull and inspect the Solo Enterprise for agentgateway Helm chart values before installation. You might want to update the Helm chart values files to customize the installation. For example, you might change the namespace, update the resource limits and requests, or enable extensions such as for AI.

      helm pull oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway --version v2026.10.2
      
      tar -xvf enterprise-agentgateway-v2026.10.2.tgz
      
      open enterprise-agentgateway/values.yaml
    2. Install Solo Enterprise for agentgateway control plane by using Helm. If you modified the values.yaml file with custom installation values, add the -f enterprise-agentgateway/values.yaml flag.

      helm upgrade -i -n agentgateway-system enterprise-agentgateway oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway \
      --version v2026.10.2  \
      --set-string licensing.licenseKey=${AGENTGATEWAY_LICENSE_KEY}
      helm upgrade -i -n agentgateway-system enterprise-agentgateway oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway \
      --version v2026.10.2 \ 
      -f enterprise-agentgateway/values.yaml \
      --set-string licensing.licenseKey=${AGENTGATEWAY_LICENSE_KEY}

      Example output:

      NAME: enterprise-agentgateway
      LAST DEPLOYED: Thu Feb 13 14:03:51 2025
      NAMESPACE: agentgateway-system
      STATUS: deployed
      REVISION: 1
      TEST SUITE: None
  5. Verify that the control plane is up and running.

    kubectl get pods -n agentgateway-system

    Example output:

    NAME                                  READY   STATUS    RESTARTS   AGE
    enterprise-agentgateway-78658959cd-cz6jt             1/1     Running   0          12s
  6. Verify that the enterprise-agentgateway GatewayClass is created. You can optionally take a look at how the GatewayClass is configured by adding the -o yaml option to your command.

    kubectl get gatewayclass enterprise-agentgateway

Next steps

Now that you have the Solo Enterprise for agentgateway control plane set up and running, check out the following guides to start using the agentgateway data plane.

Cleanup

You can remove the resources that you created in this guide.

Follow the Uninstall guide.