GEP: Mesh Conformance Testing Plan

kubernetes-sigs / gateway-api

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

https://gateway-api.sigs.k8s.io

Apache License 2.0

1.86k stars 484 forks source link

GEP: Mesh Conformance Testing Plan #1686

Open keithmattix opened 1 year ago

keithmattix commented 1 year ago

Before GAMMA is released, there needs to be, at the very least, a plan for conformance testing implementations. The level of detail for this deliverable should be something akin to this testing plan doc for sig-multicluster.

michaelbeaumont commented 1 year ago

I'd be happy to work on the testing plan

keithmattix commented 1 year ago

Current draft can be found here: https://docs.google.com/document/d/1a-MY0rBwlXGSNM4V5U0it5uLxVOpi8gTbCBipKQVn9k/edit#heading=h.pw0d9uhzxq9k

shaneutt commented 1 year ago

@michaelbeaumont should we get that reformatted into GEP format soon? doesn't seem like any of it is all that controversial, but it's a bit hard for outsiders to find nested here in a google doc? :thinking:

keithmattix commented 1 year ago

Closed by #1813

robscott commented 12 months ago

Leaving this open until this GEP either graduates to standard or is removed from the API.

/kind gep /reopen

k8s-ci-robot commented 12 months ago

@robscott: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/gateway-api/issues/1686#issuecomment-1836968990): >Leaving this open until this GEP either graduates to standard or is removed from the API. > >/kind gep >/reopen > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

k8s-triage-robot commented 9 months ago

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

youngnick commented 8 months ago

/remove-lifecycle stale /lifecycle frozen

shaneutt commented 8 months ago

Where are we at with this one, @michaelbeaumont ?

mikemorris commented 7 months ago

I believe the testing plan documented in https://github.com/kubernetes-sigs/gateway-api/pull/1813 was mostly? implemented in https://github.com/kubernetes-sigs/gateway-api/pull/1878 (would be good to double-check if any gaps remain though).

This GEP should probably be moved to Standard alongside the rest of GAMMA in https://github.com/kubernetes-sigs/gateway-api/pull/2873

youngnick commented 6 months ago

I was just reading the testing plan today (finally started working on Cilium's implementation of GAMMA), and we don't have everything covered yet. I think if we want to close this one out, we need a tracking issue for any remaining gaps.