Skip to content

gke-gateway v0.5.0 conformance test report 9/9 #1005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Jul 22, 2025
Merged
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
46 changes: 46 additions & 0 deletions conformance/reports/v0.5.0/gateway/gke-gateway/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# GKE (Google Kubernetes Engine) Gateway

## Table of Contents

| Extension Version Tested | Profile Tested | Implementation Version | Mode | Report |
|--------------------------|----------------|------------------------|---------|----------------------------------------------------------------------------|
| v0.5.0 | Gateway | 1.32.4-gke.1415000 | gke-l7-regional-external-managed | [v1.32.4 Gateway report](./standard-v1.32.4-rxlb-gateway-report.yaml) |
| ... | ... | ... | ... | ... |

## Reproduce

GKE Gateway conformance report can be reproduced by the following steps.

1. Create a GKE cluster with Gateway API enabled.

```
gcloud container clusters create "${cluster_name}" --gateway-api=standard --location="${location}"
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: variables ${cluster_name} and ${location} were not defined or referred anywhere before this line, so it could be a bit unclear for a newcomer.

do you have them defined somewhere out of this PR?
definitely not a blocker and we can make progress and come back to this if/when needed.

```
1. Deploy GKE gateway following [guide](https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-gateways#configure_a_proxy-only_subnet).
1. Install the InferencePool and InferenceModel Custom Resource Definition (CRDs) in your GKE cluster, run the following command:
```
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api-inference-extension/releases/download/v0.5.0/manifests.yaml
```
1. Run the following command from within the [Gateway API inference extension repo](https://github.com/kubernetes-sigs/gateway-api-inference-extension).
```
go test -timeout 30m ./conformance -v -args \
--gateway-class=gke-l7-regional-external-managed \
--conformance-profiles=Gateway \
--organization=GKE \
--project=gke-gateway \
--url=https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api \
--version=1.32.4-gke.1415000 \
[email protected] \
--report-output="/path/to/report"
```
or run a single conformance test case.
```
go test ./conformance -v -args \
-gateway-class=gke-l7-regional-external-managed \
-run-test=InferencePoolAccepted
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
GatewayAPIInferenceExtensionVersion: v0.5.0
apiVersion: gateway.networking.k8s.io/v1
date: "2025-07-21T22:52:10Z"
gatewayAPIChannel: standard
gatewayAPIVersion: v1.2.1
implementation:
contact:
- [email protected]
organization: GKE
project: gke-gateway
url: https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api
version: 1.32.4-gke.1415000
kind: ConformanceReport
mode: default
profiles:
- core:
result: success
statistics:
Failed: 0
Passed: 9
Skipped: 0
name: Gateway
summary: Core tests succeeded.