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.

Change shared extensions

Page as Markdown

Use built-in fields and overlays to customize the ext-auth, rate-limiter, and ext-cache deployments that the deployer automatically creates for your Gateways.

About shared extensions

When you create a Gateway, the deployer automatically provisions the following shared extension deployments in the same namespace:

  • ext-auth-service – Handles external authentication for protected routes.
  • rate-limiter – Enforces global rate limits on requests.
  • ext-cache – A Redis-backed store used by both ext-auth and rate-limiter.

You can customize these deployments by using built-in fields or overlays in the spec.sharedExtensions section of the EnterpriseAgentgatewayParameters resource, and then attaching the resource to a GatewayClass.

Note

Extension settings are shared across all Gateways that use the same GatewayClass. Attach the EnterpriseAgentgatewayParameters resource to a GatewayClass, not to individual Gateways.

Before you begin

  1. Follow the Get started guide to install Solo Enterprise for agentgateway.

  2. Follow the Sample app guide to create a gateway proxy with an HTTP listener and deploy the httpbin sample app.

  3. Get the external address of the gateway and save it in an environment variable.

    export INGRESS_GW_ADDRESS=$(kubectl get svc -n agentgateway-system http -o jsonpath="{.status.loadBalancer.ingress[0]['hostname','ip']}")
    echo $INGRESS_GW_ADDRESS  
    kubectl port-forward deployment/http -n agentgateway-system 8080:8080

Customize shared extensions

Choose between the following options to customize your extensions:

Built-in customization

Use the built-in resources field to set CPU and memory requests and limits for an extension.

  1. Create a EnterpriseAgentgatewayParameters resource with your resource settings in the sharedExtensions section. The following example updates the resource requests and limits for a shared extension.

    kubectl apply -f- <<EOF
    apiVersion: enterpriseagentgateway.solo.io/v1alpha1
    kind: EnterpriseAgentgatewayParameters
    metadata:
      name: ext-params
      namespace: agentgateway-system
    spec:
      sharedExtensions:
        extauth:
          enabled: true
          resources:
            requests:
              cpu: 200m
              memory: 256Mi
            limits:
              cpu: 750m
              memory: 512Mi
        ratelimiter:
          enabled: true
          resources:
            requests:
              cpu: 200m
              memory: 256Mi
            limits:
              cpu: 750m
              memory: 512Mi
        extCache:
          enabled: true
          resources:
            requests:
              cpu: 256m
              memory: 512Mi
            limits:
              cpu: 1000m
              memory: 2048Mi
    EOF
  2. Update the GatewayClass to reference the new EnterpriseAgentgatewayParameters resource.

    kubectl apply -f- <<EOF
    apiVersion: gateway.networking.k8s.io/v1
    kind: GatewayClass
    metadata:
      name: enterprise-agentgateway
    spec:
      controllerName: solo.io/enterprise-agentgateway
      parametersRef:
        group: enterpriseagentgateway.solo.io
        kind: EnterpriseAgentgatewayParameters
        name: ext-params
        namespace: agentgateway-system
    EOF
  3. Verify that the resource changes are applied to the deployments.

    Use labels to select the Deployments instead of exact Deployment names. The app labels are present across versions, while the rate-limiter and ext-cache Deployment names can include a selector-revision suffix after an upgrade.

    echo "ext-auth-service"
    kubectl get deployment -l app=ext-auth-service \
      -n agentgateway-system \
      -o json | jq '.items[].spec.template.spec.containers[0].resources'
    
    echo "ext-cache"
    kubectl get deployment -l app=ext-cache \
      -n agentgateway-system \
      -o json | jq '.items[].spec.template.spec.containers[0].resources'
    
    echo "rate-limiter"
    kubectl get deployment -l app=rate-limiter \
      -n agentgateway-system \
      -o json | jq '.items[].spec.template.spec.containers[0].resources'

    Example output:

    ext-auth-service
    {
     "limits": {
       "cpu": "750m",
       "memory": "512Mi"
     },
     "requests": {
       "cpu": "200m",
       "memory": "256Mi"
     }
    }
    ext-cache
    {
     "limits": {
       "cpu": "1",
       "memory": "2Gi"
     },
     "requests": {
       "cpu": "256m",
       "memory": "512Mi"
     }
    }
    rate-limiter
    {
     "limits": {
       "cpu": "750m",
       "memory": "512Mi"
     },
     "requests": {
       "cpu": "200m",
       "memory": "256Mi"
     }
    }
    

Overlays

Use overlay fields to apply a strategic merge patch to the generated extension Kubernetes resources. For more examples, see the Overlay examples.

  1. Create a EnterpriseAgentgatewayParameters resource with your overlay settings. In this example, you use the deployment option to add custom labels and annotations to the ext-auth-service and rate-limiter deployments.

    kubectl apply --server-side -f- <<'EOF'
    apiVersion: enterpriseagentgateway.solo.io/v1alpha1
    kind: EnterpriseAgentgatewayParameters
    metadata:
      name: ext-params
      namespace: agentgateway-system
    spec:
      sharedExtensions:
        extauth:
          enabled: true
          deployment:
            metadata:
              labels:
                team: security
                environment: production
            spec:
              template:
                metadata:
                  annotations:
                    app.kubernetes.io/part-of: "api-gateway"
                    support-channel: "slack://security-alerts"
        ratelimiter:
          enabled: true
          deployment:
            metadata:
              labels:
                team: platform
    EOF
  2. Update the GatewayClass to reference the new EnterpriseAgentgatewayParameters resource.

    kubectl apply -f- <<EOF
    apiVersion: gateway.networking.k8s.io/v1
    kind: GatewayClass
    metadata:
      name: enterprise-agentgateway
    spec:
      controllerName: solo.io/enterprise-agentgateway
      parametersRef:
        group: enterpriseagentgateway.solo.io
        kind: EnterpriseAgentgatewayParameters
        name: ext-params
        namespace: agentgateway-system
    EOF
  3. Verify that the labels and annotations are applied to the ext-auth-service and rate-limiter Deployments.

    kubectl get deployment -l app=ext-auth-service \
      -n agentgateway-system \
      -o json | jq '.items[].metadata.labels'
    
    kubectl get deployment -l app=ext-auth-service \
      -n agentgateway-system \
      -o json | jq '.items[].spec.template.metadata.annotations'
    
    kubectl get deployment -l app=rate-limiter \
      -n agentgateway-system \
      -o json | jq '.items[].metadata.labels'

    Example output:

    {
      "app": "ext-auth-service",
      "environment": "production",
      "gateway.solo.io/extension": "solo-ext-auth",
      "gateway.solo.io/gatewayclass": "enterprise-agentgateway",
      "team": "security"
    }
    {
      "app.kubernetes.io/part-of": "api-gateway",
      "prometheus.io/path": "/metrics",
      "prometheus.io/port": "9091",
      "prometheus.io/scrape": "true",
      "support-channel": "slack://security-alerts"
    }
    {
      "app": "rate-limiter",
      "gateway.solo.io/extension": "solo-rate-limiter",
      "gateway.solo.io/gatewayclass": "enterprise-agentgateway",
      "team": "platform"
    }
    

Cleanup

You can optionally remove the resources that you set up as part of this guide.
  1. Remove the parametersRef from the GatewayClass to restore the default configuration.

    kubectl apply -f- <<EOF
    apiVersion: gateway.networking.k8s.io/v1
    kind: GatewayClass
    metadata:
      name: enterprise-agentgateway
    spec:
      controllerName: solo.io/enterprise-agentgateway
    EOF
  2. Delete the EnterpriseAgentgatewayParameters resource.

    kubectl delete EnterpriseAgentgatewayParameters ext-params -n agentgateway-system