Skip to content

Add conformance report for Contour 1.33.0 and Gateway API 1.3.0 - #4076

Merged
k8s-ci-robot merged 2 commits into
kubernetes-sigs:mainfrom
sunjayBhatia:contour-1.33.0-conformance-report
Apr 6, 2026
Merged

k8s-ci-robot merged 2 commits into
kubernetes-sigs:mainfrom
sunjayBhatia:contour-1.33.0-conformance-report

Conversation

@sunjayBhatia

Copy link
Copy Markdown
Member

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Adds conformance report for new Contour 1.33.0 release which supports Gateway API 1.3.0

Which issue(s) this PR fixes:

N/A

Does this PR introduce a user-facing change?:

NONE

Signed-off-by: Sunjay Bhatia <sunjay.bhatia@broadcom.com>
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 9, 2025
@sunjayBhatia

Copy link
Copy Markdown
Member Author

cc @kubernetes-sigs/gateway-api-maintainers

@robscott robscott left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks @sunjayBhatia!

Comment on lines +69 to +72
skippedTests:
- GatewayStaticAddresses
- HTTPRouteInvalidParentRefSectionNameNotMatchingPort
- HTTPRouteRedirectPortAndScheme

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Instead of skipping tests can you just change the set of features you claim to support?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@robscott I did re-run conformance with unsupported features rather than specific skipped tests, though it does mean some tests that do pass are not run/documented as such any longer

Hoping to cover all of these in our next release and with 1.4.0 conformance so not a huge deal

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I wasn't able to stop skipping the HTTPRouteHTTPSListener test as there is no specific feature associated with the test, it would mean skipping all HTTPRoute tests which is not ideal of course

Signed-off-by: Sunjay Bhatia <sunjay.bhatia@broadcom.com>
- core:
result: partial
skippedTests:
- HTTPRouteHTTPSListener

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

had to leave this as a skipped test since there is not a specific enough feature to disable this one test (otherwise we would have to disable testing HTTPRoute in general), this should be addressed in the next release however to remove the skip entirely

unsupportedFeatures:
- GatewayStaticAddresses
- HTTPRouteParentRefPort
- HTTPRoutePortRedirect

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

note: passing HTTPRouteParentRefPort and HTTPRoutePortRedirect as unsupported means we're now skipping running some tests that do pass, the specific tests that were previously skipped are HTTPRouteRedirectPortAndScheme and HTTPRouteInvalidParentRefSectionNameNotMatchingPort

@k8s-triage-robot

Copy link
Copy Markdown

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 11, 2026
@k8s-triage-robot

Copy link
Copy Markdown

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 13, 2026
@rikatz

rikatz commented Apr 6, 2026

Copy link
Copy Markdown
Member

I think we can merge this, given Contour have users. But we need to be aware that some recent cleanup for stale implementations may start soon

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 6, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz, sunjayBhatia

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 6, 2026
@k8s-ci-robot
k8s-ci-robot merged commit 0cbcbdb into kubernetes-sigs:main Apr 6, 2026
5 checks passed
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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. 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.

5 participants