chore: add conformance report for KIC 3.2.0#3152
Conversation
|
|
|
Welcome @czeslavo! |
|
Hi @czeslavo. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
3ecf50b to
6f47824
Compare
|
|
||
| | API channel | Implementation version | Mode | Report | | ||
| |-------------|-------------------------------------------------------------------------------------|------|------------------------------| | ||
| | x | [v3.2.0](https://github.com/Kong/kubernetes-ingress-controller/releases/tag/v3.2.0) | x | [link](./v3.2.0-report.yaml) | |
There was a problem hiding this comment.
We need to rename the report according to the rules stated here: https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/README.md
6f47824 to
11709d1
Compare
|
|
||
| | API channel | Implementation version | Mode | Report | | ||
| |--------------|-------------------------------------------------------------------------------------|-------------|------------------------------| | ||
| | experimental | [v3.2.0](https://github.com/Kong/kubernetes-ingress-controller/releases/tag/v3.2.0) | expressions | [link](./v3.2.0-report.yaml) | |
There was a problem hiding this comment.
We need to update the report link here, along with its rename.
There was a problem hiding this comment.
Good catch, missed that one. Thanks :)
11709d1 to
226c967
Compare
226c967 to
426e1e6
Compare
|
Thanks @czeslavo! /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: czeslavo, robscott The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
/area conformance
What this PR does / why we need it:
Adds a Gateway API v1.1.0 conformance report for Kong's Kubernetes Ingress Controller v3.2.0.
Does this PR introduce a user-facing change?: