Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions conformance/reports/v1.0.1/gateway/envoy-ai-gateway/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Envoy AI Gateway

## Table of Contents

| Extension Version Tested | Profile Tested | Implementation Version | Mode | Report |
|--------------------------|----------------|------------------------|---------|-----------------------------------------------------------------------|
| v1.0.1 | Gateway | [latest](https://github.com/envoyproxy/ai-gateway) | default | [Conformance report](./aigw-latest-report.yaml) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great. can you only update the version here instead of latest?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

latest is the current main, since we didnt have a major release for this, will be updated after we had a release

Copy link
Contributor

@nirrozenbaum nirrozenbaum Oct 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mmmm. I think it might become a bit tricky.
we had the same thing in previous release v0.5.1 with this report:
https://github.com/kubernetes-sigs/gateway-api-inference-extension/tree/main/conformance/reports/v0.5.1/gateway/envoy-ai-gateway

usually if there is no issue tracker or opened PR nothing triggers this update (as we can see in v0.5.1).

can you at least update to the release branch if there is such?
kGateway for example updated using their latest release branch (release wasn't cut yet), but at least we know which release is correlated to this version. see example here:
https://github.com/kubernetes-sigs/gateway-api-inference-extension/tree/main/conformance/reports/v1.0.0/gateway/kgateway

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let me see if we can have a minor release for this

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we will cut a release soon by the end of the month

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! Just checking in on the status here

| ... | ... | ... | ... | ... |

## Reproduce

This is a mirror of the envoy ai gateway [conformance e2e test](https://github.com/envoyproxy/ai-gateway/blob/main/.github/workflows/build_and_test.yaml), which includes the conformance tests for the Gateway API and Inference Extension.

### Prerequisites

In order to run the conformance tests, the following prerequisites must be met:

- The [kubectl](https://kubernetes.io/docs/tasks/tools/) command-line tool installed and configured for the active cluster context.
- The [helm](https://github.com/helm/helm),[kind](https://kind.sigs.k8s.io), [git](https://git-scm.com/downloads), and [make](https://www.gnu.org/software/make/) command-line tools installed.

### Steps

1. Clone the envoy-ai-gateway repository and checkout the release:

```sh
git clone https://github.com/envoyproxy/ai-gateway.git && cd ai-gateway
```

2. Running the Gateway API Inference Extension conformance tests:

```sh
make test-e2e-inference-extension TEST_KEEP_CLUSTER=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I followed the steps in this reproducer, but it failed:

$ make test-e2e-inference-extension TEST_KEEP_CLUSTER=true
...
daemonset.apps/speaker serverside-applied
validatingwebhookconfiguration.admissionregistration.k8s.io/metallb-webhook-configuration serverside-applied
=== INIT LOG: 	Creating memberlist secret if needed
=== INIT LOG: 	Waiting for MetalLB controller deployment to be ready
error: unrecognized condition: "create"
=== INIT LOG: 	done (took 0.64s in total)
=== CLEANUP LOG: Collecting logs from the kind cluster
Exporting logs for cluster "envoy-ai-gateway" to:
./logs
Failed to set up the test environment: failed to initialize MetalLB: failed to wait for MetalLB controller: error waiting for deployment controller in namespace metallb-system: exit status 1
FAIL	github.com/envoyproxy/ai-gateway/tests/e2e-inference-extension	5.199s
FAIL
make: *** [test-e2e-inference-extension] Error 1

$ less ./logs
./logs: No such file or directory

$ kubectl get po -n metallb-system
NAME                          READY   STATUS    RESTARTS   AGE
controller-5c8796d8b6-c9rr7   1/1     Running   0          4m26s
speaker-l9xxs                 1/1     Running   0          4m25s

$ git pull origin
Already up to date.

```
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
GatewayAPIInferenceExtensionVersion: v1.0.1
apiVersion: gateway.networking.k8s.io/v1
date: "2025-10-11T00:33:01Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.3.0
implementation:
contact:
- '@envoy-ai-gateway/maintainers'
organization: EnvoyProxy
project: Envoy AI Gateway
url: https://github.com/envoyproxy/ai-gateway
version: latest
kind: ConformanceReport
mode: default
profiles:
- core:
result: success
statistics:
Failed: 0
Passed: 9
Skipped: 0
name: Gateway
summary: Core tests succeeded.