GEP: Mesh Conformance Testing Plan

[keithmattix]

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]

I'd be happy to work on the testing plan

[keithmattix]

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

[shaneutt]

@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? 🤔

[keithmattix]

Closed by #1813

[robscott]

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

/kind gep
/reopen

[k8s-ci-robot]

@robscott: Reopened this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

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]

/remove-lifecycle stale
/lifecycle frozen

[shaneutt]

Where are we at with this one, @michaelbeaumont ?

[mikemorris]

I believe the testing plan documented in #1813 was mostly? implemented in #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 #2873

[youngnick]

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.

[k8s-triage-robot]

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[mikemorris]

/remove-lifecycle rotten

Still some outstanding work here to identify remaining conformance gaps per #1686 (comment).

Refs #3566

[LiorLieberman]

and #3581