rvennam

Enterprise agentgateway on OpenShift — install guide

Installs the enterprise agentgateway control plane, a data-plane gateway, and the Solo management UI (cost dashboards, ClickHouse, telemetry collector) on OpenShift 4.19+ using Helm. Written for OpenShift 4.21: the Kubernetes Gateway API ships with the platform, so there is nothing to install for it.

Everything lands in the docs-default namespace agentgateway-system.

Tested end to end on ARO / OpenShift 4.20.15 with the platform-managed Gateway API CRDs (standard channel v1.2.1): all pods scheduled under the default SCCs with the settings below, the Gateway programmed, LLM traffic flowed through the external Route, and traces landed in ClickHouse for the UI.

Prerequisites

rvennam

apiVersion: v1
kind: Namespace
metadata:
  name: egress-direct
  labels:
    istio.io/dataplane-mode: ambient
---
apiVersion: v1
kind: Namespace
metadata:

rvennam

Workshop: Native AWS Bedrock AgentCore Routing with Solo Enterprise Agent Gateway v2.3.0

Overview

Solo Enterprise Agent Gateway v2.3.0 introduces native AWS Bedrock AgentCore backend support — no sidecar proxy, no custom container, no extra hop. The gateway signs requests with SigV4 using the correct bedrock-agentcore service name and routes A2A traffic directly to your AgentCore runtime agents.

In this workshop you will:

1. Install Enterprise Agent Gateway v2.3.0 on EKS
2. Configure IRSA so the gateway can call AgentCore natively

rvennam

Production Observability, Alerting, and Scaling

This guide covers production-readiness for Enterprise AgentGateway: a complete metrics reference, recommended Prometheus alerting rules, horizontal pod autoscaling, graceful shutdown for long-lived AI connections, pod spreading, disruption budgets, and zero-downtime upgrades.

---

Metrics Reference

Enterprise AgentGateway exposes metrics from three components.

rvennam

Install Agentgateway (Open Source)

In this workshop, you'll deploy the open-source Agentgateway and complete hands-on labs that showcase routing, observability, and Gen AI features.

Pre-requisites

• Kubernetes > 1.30
• Kubernetes Gateway API
• helm package manager installed

Lab Objectives

rvennam

Route to a Remote A2A Agent by Hostname

Pre-requisites

This lab assumes that you have completed the setup in 001 and 002

Lab Objectives

• Route to a remote A2A agent by hostname (not IP address) through AgentGateway
• Preserve full A2A protocol detection, including "protocol":"a2a" and a2a.method in access logs
• Handle port and path differences on the remote agent
• Validate A2A connectivity and observability through the gateway

rvennam

Global Rate Limiting with External Redis

Lab Objectives

• Deploy an external Redis instance separate from the built-in ext-cache
• Configure the Enterprise AgentGateway rate limiter to use the external Redis via a deployment overlay
• Apply global rate limiting to LLM routes using RateLimitConfig and EnterpriseAgentgatewayPolicy
• Verify rate limit counters are stored in the external Redis

Overview

rvennam

Configure Route to Remote A2A Agent

Pre-requisites

This lab assumes that you have completed the setup in 001 and 002

Lab Objectives

• Deploy a mock A2A agent and expose it as a remote service
• Route to the remote A2A agent through AgentGateway
• Validate A2A connectivity through the gateway
• Observe A2A traffic in access logs

rvennam

Solo Enterprise for Agentgateway - Feature List

A comprehensive list of functional features available in Solo Enterprise for Agentgateway, categorized by LLM and MCP capabilities.

---

LLM Features

Multi-Provider Routing

• Route to OpenAI

rvennam

{
  "policies": [
    {
      "key": "backend/enterprise-agentgateway/aliases-policy:ai:enterprise-agentgateway/openai",
      "name": {
        "kind": "AgentgatewayPolicy",
        "name": "aliases-policy",
        "namespace": "enterprise-agentgateway"
      },
      "target": {