<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Conformance on KubernetesLab</title><link>https://kuberneteslab.dev/en/tags/conformance/</link><description>Recent content in Conformance on KubernetesLab</description><image><title>KubernetesLab</title><url>https://kuberneteslab.dev/images/og-brand.png</url><link>https://kuberneteslab.dev/images/og-brand.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kuberneteslab.dev/en/tags/conformance/index.xml" rel="self" type="application/rss+xml"/><item><title>Passing Conformance Isn't Enough: Re-scoring 7 Gateway API Implementations from Scratch</title><link>https://kuberneteslab.dev/en/blog/gateway-api-poc-v1.4/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://kuberneteslab.dev/en/blog/gateway-api-poc-v1.4/</guid><description>After Ingress NGINX retired, which Gateway API should you move to? We rebuilt last year&amp;#39;s PoC around the official conformance model and re-measured 7 implementations from scratch. All 7 pass the required features, but their actual feature breadth splits from 6 to 13, and Kong and Traefik, which scored low last year, are now among those that pass.</description></item></channel></rss>