Skip to content

docs: better feature comparison table - #4744

Merged
k8s-ci-robot merged 1 commit into
kubernetes-sigs:mainfrom
howardjohn:docs/better-compare-table
Apr 17, 2026
Merged

k8s-ci-robot merged 1 commit into
kubernetes-sigs:mainfrom
howardjohn:docs/better-compare-table

Conversation

@howardjohn

@howardjohn howardjohn commented Apr 10, 2026 •

Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind documentation

What this PR does / why we need it:
Before, we attempted to look at the Go tests to map a test to 'experimental' or 'not experimental'. This gives some weird results, not to mention only one is considered experimental. It didn't really make sense.

Now we report directly from the YAML file. All implementations across all versions currently pass all core features, so we focus on extended ones. If in the future one fails a core feature, it gets an explicit warning added. like Failing 1/33 core tests. By default, it just says something like 28/35 supported features. Partially conformant entries will get a message added like Partially conformant; 3/53 tests skipped.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

NONE

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 10, 2026
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 10, 2026
Before, we attempted to look at the Go tests to map a test to
'experimental' or 'not experimental'. This gives some weird results, not
to mention only one is considered experimental. It didn't really make
sense.

Now we report directly from the YAML file. All implementations across
all versions currently pass all core features, so we focus on extended
ones. If in the future one fails a core feature, it gets an explicit
warning added. like `Failing 1/33 core tests`. By default, it just says
something like `28/35 supported features`. Partially conformant entries
will get a message added like `Partially conformant; 3/53 tests
skipped`.
@howardjohn
howardjohn force-pushed the docs/better-compare-table branch from ab59679 to c9d8414 Compare April 10, 2026 21:34
@youngnick

Copy link
Copy Markdown
Contributor

Changes LGTM, but it looks like they've only taken effect for v1.5?

@howardjohn

Copy link
Copy Markdown
Contributor Author

@youngnick not sure what you mean? they are on v1.4 as well for me?

2026-04-13_12-01-11

@youngnick

Copy link
Copy Markdown
Contributor

Yeah, I don't know what was going on last time, I swear I didn't see it in the earlier versions.

This LGTM now.

/approve

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: howardjohn, youngnick

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2026
@keithmattix

Copy link
Copy Markdown
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 17, 2026
@k8s-ci-robot
k8s-ci-robot merged commit 0fb4617 into kubernetes-sigs:main Apr 17, 2026
32 checks passed
ericdbishop pushed a commit to ericdbishop/gateway-api that referenced this pull request Apr 22, 2026
Before, we attempted to look at the Go tests to map a test to
'experimental' or 'not experimental'. This gives some weird results, not
to mention only one is considered experimental. It didn't really make
sense.

Now we report directly from the YAML file. All implementations across
all versions currently pass all core features, so we focus on extended
ones. If in the future one fails a core feature, it gets an explicit
warning added. like `Failing 1/33 core tests`. By default, it just says
something like `28/35 supported features`. Partially conformant entries
will get a message added like `Partially conformant; 3/53 tests
skipped`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants