refactor: move envoy gateway configmap to values.yaml files (#1410)

**Description**

Envoy AI Gateway currently requires an envoy gateway config map to be
overriden. The better approach is to pass the configmap as helm values
during envoy gateway helm install. This PR makes changes to the
documentation and installation files to do the same.

**Related Issues/PRs (if applicable)**

Fixes: #1191

---------

Signed-off-by: sailesh duddupudi <[email protected]>

Author: saileshd1402

examples/inference-pool/README.md

@@ -0,0 +1,56 @@
+# InferencePool Example
+
+This example demonstrates how to use AI Gateway with the InferencePool feature, which enables intelligent request routing across multiple inference endpoints with load balancing and health checking capabilities.
+
+## Files in This Directory
+
+- **`envoy-gateway-values-addon.yaml`**: Envoy Gateway values addon for InferencePool support. Combine with `../../manifests/envoy-gateway-values.yaml`.
+- **`base.yaml`**: Complete example that includes Gateway, AIServiceBackend, InferencePool CRDs, and a sample application deployment.
+- **`aigwroute.yaml`**: Example AIGatewayRoute that uses InferencePool as a backend.
+- **`httproute.yaml`**: Example HTTPRoute for traditional HTTP routing to InferencePool endpoints.
+- **`with-annotations.yaml`**: Advanced example showing InferencePool with Kubernetes annotations for fine-grained control.
+
+## Quick Start
+
+1. Install Envoy Gateway with InferencePool support:
+
+   ```bash
+   helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+     --version v0.0.0-latest \
+     --namespace envoy-gateway-system \
+     --create-namespace \
+     -f ../../manifests/envoy-gateway-values.yaml \
+     -f envoy-gateway-values-addon.yaml
+   ```
+
+2. Deploy the example:
+
+   ```bash
+   kubectl apply -f base.yaml
+   ```
+
+3. Test the setup:
+
+   ```bash
+   GATEWAY_HOST=$(kubectl get gateway/ai-gateway -o jsonpath='{.status.addresses[0].value}')
+   curl -X POST "http://${GATEWAY_HOST}/v1/chat/completions" \
+     -H "Content-Type: application/json" \
+     -d '{"model": "gpt-3.5-turbo", "messages": [{"role": "user", "content": "Hello!"}]}'
+   ```
+
+### Combining with Other Features
+
+You can easily combine InferencePool with other features using multiple `-f` flags:
+
+```bash
+# InferencePool + rate limiting
+helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+  --version v0.0.0-latest \
+  --namespace envoy-gateway-system \
+  --create-namespace \
+  -f ../basic/envoy-gateway-values.yaml \
+  -f ../token_ratelimit/envoy-gateway-values-addon.yaml \
+  -f envoy-gateway-values-addon.yaml
+```
+
+For detailed documentation, see the [AI Gateway documentation](https://gateway.envoyproxy.io/ai-gateway/).

examples/inference-pool/config.yaml

@@ -0,0 +1,28 @@
+# Copyright Envoy AI Gateway Authors
+# SPDX-License-Identifier: Apache-2.0
+# The full text of the Apache license is available in the LICENSE file at
+# the root of the repo.
+
+# This addon file adds InferencePool support to Envoy Gateway.
+# Use this in combination with the base envoy-gateway-values.yaml:
+#
+#   helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+#     --version v0.0.0-latest \
+#     --namespace envoy-gateway-system \
+#     --create-namespace \
+#     -f ../../manifests/envoy-gateway-values.yaml \
+#     -f envoy-gateway-values-addon.yaml
+#
+# You can also combine with rate limiting:
+#   -f ../../manifests/envoy-gateway-values.yaml \
+#   -f ../token_ratelimit/envoy-gateway-values-addon.yaml \
+#   -f envoy-gateway-values-addon.yaml
+
+config:
+  envoyGateway:
+    extensionManager:
+      # Enable InferencePool custom resource support
+      backendResources:
+        - group: inference.networking.k8s.io
+          kind: InferencePool
+          version: v1

examples/inference-pool/envoy-gateway-values-addon.yaml

@@ -1,4 +1,53 @@
+# Token based ratelimiting
+
 This example demonstrates how to use the token rate limit feature of the AI Gateway.
 This utilizes the Global Rate Limit API of Envoy Gateway combined with the
 AI Gateway's `llmRequestCosts` configuration to capture the consumed tokens
 of each request.
+
+## Files in This Directory
+
+- **`envoy-gateway-values-addon.yaml`**: Envoy Gateway values addon for rate limiting. Combine with `../../manifests/envoy-gateway-values.yaml`.
+- **`redis.yaml`**: Redis deployment required for rate limiting. Deploy this before enabling rate limiting in Envoy Gateway.
+- **`token_ratelimit.yaml`**: Example AIGatewayRoute configuration that demonstrates token-based rate limiting.
+
+## Quick Start
+
+1. Install Envoy Gateway with base configuration + rate limiting addon:
+
+   ```bash
+   helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+     --version v0.0.0-latest \
+     --namespace envoy-gateway-system \
+     --create-namespace \
+     -f ../../manifests/envoy-gateway-values.yaml \
+     -f envoy-gateway-values-addon.yaml
+   ```
+
+2. Deploy Redis:
+
+   ```bash
+   kubectl apply -f redis.yaml
+   ```
+
+3. Apply the token rate limit example:
+   ```bash
+   kubectl apply -f token_ratelimit.yaml
+   ```
+
+### Combining with Other Features
+
+You can easily combine rate limiting with other features using multiple `-f` flags:
+
+```bash
+# Rate limiting + InferencePool support
+helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+  --version v0.0.0-latest \
+  --namespace envoy-gateway-system \
+  --create-namespace \
+  -f ../basic/envoy-gateway-values.yaml \
+  -f envoy-gateway-values-addon.yaml \
+  -f ../inference-pool/envoy-gateway-values-addon.yaml
+```
+
+For detailed documentation, see the [usage-based rate limiting guide](https://gateway.envoyproxy.io/ai-gateway/docs/capabilities/traffic/usage-based-ratelimiting).

examples/token_ratelimit/README.md

@@ -0,0 +1,40 @@
+# Copyright Envoy AI Gateway Authors
+# SPDX-License-Identifier: Apache-2.0
+# The full text of the Apache license is available in the LICENSE file at
+# the root of the repo.
+
+# This addon file adds rate limiting configuration to Envoy Gateway.
+# Use this in combination with the base envoy-gateway-values.yaml:
+#
+#   helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+#     --version v0.0.0-latest \
+#     --namespace envoy-gateway-system \
+#     --create-namespace \
+#     -f ../../manifests/envoy-gateway-values.yaml \
+#     -f envoy-gateway-values-addon.yaml
+#
+# Prerequisites:
+# - Redis must be deployed (see redis.yaml in this directory)
+
+config:
+  envoyGateway:
+    provider:
+      kubernetes:
+        rateLimitDeployment:
+          patch:
+            type: StrategicMerge
+            value:
+              spec:
+                template:
+                  spec:
+                    containers:
+                      - imagePullPolicy: IfNotPresent
+                        name: envoy-ratelimit
+                        image: docker.io/envoyproxy/ratelimit:60d8e81b
+    rateLimit:
+      backend:
+        type: Redis
+        redis:
+          # Update this URL to match your Redis service location
+          # This assumes Redis is deployed using the redis.yaml in this directory
+          url: redis.redis-system.svc.cluster.local:6379

examples/token_ratelimit/envoy-gateway-values-addon.yaml

@@ -4,7 +4,11 @@
 # the root of the repo.
 
 # This is a simple example of a Redis deployment that is used
-# by the default Envoy Gateway setting in config.yaml. TODO: modify this comment when https://github.com/envoyproxy/ai-gateway/issues/1191 is fixed.
+# by the Envoy Gateway rate limiting feature.
+#
+# This is only necessary if you want to use the rate limit feature.
+# When enabling rate limiting, you need to configure Envoy Gateway to point to this Redis instance.
+# See the envoy-gateway-values-addon.yaml file in this directory for the complete configuration example.
 ---
 kind: Namespace
 apiVersion: v1

examples/token_ratelimit/redis.yaml

@@ -0,0 +1,57 @@
+# Copyright Envoy AI Gateway Authors
+# SPDX-License-Identifier: Apache-2.0
+# The full text of the Apache license is available in the LICENSE file at
+# the root of the repo.
+
+# This file contains the base Envoy Gateway helm values needed for AI Gateway integration.
+# This is the minimal configuration that all AI Gateway deployments need.
+#
+# Use this file when installing Envoy Gateway with:
+#   helm upgrade -i eg oci://docker.io/envoyproxy/gateway-helm \
+#     --version v0.0.0-latest \
+#     --namespace envoy-gateway-system \
+#     --create-namespace \
+#     -f envoy-gateway-values.yaml
+#
+# For additional features, combine with addon values files:
+#   -f envoy-gateway-values.yaml -f examples/token_ratelimit/envoy-gateway-values-addon.yaml
+#   -f envoy-gateway-values.yaml -f examples/inference-pool/envoy-gateway-values-addon.yaml
+
+config:
+  envoyGateway:
+    gateway:
+      controllerName: gateway.envoyproxy.io/gatewayclass-controller
+    logging:
+      level:
+        default: info
+    provider:
+      type: Kubernetes
+    extensionApis:
+      # Not strictly required, but recommended for backward/future compatibility.
+      enableEnvoyPatchPolicy: true
+      # Required: Enable Backend API for AI service backends.
+      enableBackend: true
+    # Required: AI Gateway needs to fine-tune xDS resources generated by Envoy Gateway.
+    extensionManager:
+      hooks:
+        xdsTranslator:
+          translation:
+            listener:
+              includeAll: true
+            route:
+              includeAll: true
+            cluster:
+              includeAll: true
+            secret:
+              includeAll: true
+          post:
+            - Translation
+            - Cluster
+            - Route
+      service:
+        fqdn:
+          # IMPORTANT: Update this to match your AI Gateway controller service
+          # Format: <service-name>.<namespace>.svc.cluster.local
+          # Default if you followed the installation steps above:
+          hostname: ai-gateway-controller.envoy-ai-gateway-system.svc.cluster.local
+          port: 1063