V1.5 Implementations page review

[youngnick]

What type of PR is this?
/kind cleanup
/kind documentation

What this PR does / why we need it:

This PR performs the Implementations Page Review process for Gateway API v1.5, as documented in the Page Review Policy.

Opening this PR starts the two-week right-of-reply period, which means that this PR will be merged and take effect at midday AEST, Friday, 24th April 2026. (That's Australian time, which means that it's Thursday evening in the US, and early Friday morning in Europe. Basically, you have until EOD Thursday 23rd April if you're anywhere other than Australia.)

Note that changes to this PR are possible during the right-of-reply period. If an implementation gets a conformance report merged, please notify me (@youngnick) on this PR by replying in a comment with the PR where the conformance report is merged, and I will update accordingly.

Full conformance requires:

• A conformance report for one of the last two versions of Gateway API (v1.5 or v1.4), or a patch release in those minor versions.
• The conformance report must have at least one profile that fully passes the conformance test suite for that profile, with zero skipped tests for that profile. All other profiles must be at least partially conformant.

Partial conformance requires:

• A conformance report for one of the last three versions of Gteway API (v1.5, v1.4, or v1.3), or a patch release in those minor versions.
• The conformance report must have all claimed profiles show at least partial conformance results.

This marks the first release where Stale implementations are being removed from the Implementations page. Implementations that were stale in the v1.4 Implementations Page review are being removed from the page. In v1.6, the Stale category will be removed entirely, and implementations must be Conformant or Partially Conformant to be listed on this page.

There were a lot of changes this time:

Gateway Changes:

Conformant -> Partially Conformant

• Envoy Gateway

Partially Conformant -> Stale

• Azure Application Gateway for Containers
• Kong Ingress Controller
• Kubvernor

Stale -> Conformant:

• Gloo Gateway

Stale -> Partially Conformant:

• Amazon Elastic Kubernetes Service

Stale -> Removed:

• Acnodal EPIC
• Apache APISIX
• Avi Kubernetes Operator
• Easegress
• Emissary-Ingress (Ambassador API Gateway)
• Flomesh Service Mesh
• HAProxy Kubernetes Ingress Controller
• HashiCorp Consul
• Kuma
• LiteSpeed Ingress Controller
• LoxiLB
• ngrok
• STUNner
• Tyk
• WSO2 APK

Mesh Changes:

Conformant -> Partially Conformant

• Alibaba Cloud Service Mesh
• Linkerd

Stale -> Removed:

• Google Cloud Service Mesh
• Kuma

NONE

[youngnick]

/hold

for right-of-reply period.

[snorwin]

I think Envoy Gateway should be listed as conformant, according to #4715

@zirain @zhaohuabing

[zirain]

yes, EG should be listed.

[youngnick]

Thanks folks, I had missed that conformance report, I will update.

[zirain]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: snorwin, youngnick, zirain

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• site-src/OWNERS [youngnick]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[davidjumani]

Added conformance reports in #4757

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[youngnick]

Hmm, after updating, I went and checked the conformance report for Envoy Gateway, and all of the submitted conformance reports have partial results for all claimed profiles (due to skipped tests). So Envoy Gateway only meets the criteria for Partial Conformance.

I should also note that the listed release version of Envoy Gateway is not a tagged release in the Envoy Gateway repo, which is not what's intended for conformance reports. Please ensure that the version of the software is one that users can actually download and use in future conformance reports.