[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: michaelbeaumont
Once this PR has been reviewed and has the lgtm label, please assign thockin for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

PR needs rebase.

First, thanks for the GEP. It looks good and seems like a reasonable path for this if we decide to go with it.

In my subjective opinion this doesn't help the project meaningfully. We are adding complexity that doesn't hold it's own weight in user benefit. FWIW I think the same about GatewayClass, though, so that may be an unpopular opinion :-)

Basically we are making a new resource (high cost!) with the idea that maybe we want to do things with it in the future (this is not convincing at all; we shouldnt weight hypotheticals highly) and to report some information.

This can, and imo should, simply be a page on a projects' documentation. This is orders of magnitude simpler while still providing as much (if not more!) value to users

We appreciate your thoughts as always @howardjohn. These comments do seem to unfortunately provide slight ambiguity as to the prescription or specific actions to take on your behalf, however. The best read I can come up with of what action you may be prescribing is "don't proceed until we have stronger use cases / user stories". If that's the case I think asking for more and stronger emphasis on use cases and user stories seems legit, though I don't personally feel that it needs to hold us up from reaching a Provisional state.

In any case it would seem prudent for many of us who focus on GAMMA to give this some deep through and review it:

/cc @kflynn @keithmattix @mikemorris @whitneygriffith

Please review and share your thoughts and ideas about the Mesh resource concept.

@shaneutt: GitHub didn't allow me to request PR reviews from the following users: whitneygriffith.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

I'll close this PR until we can discuss Mesh further elsewhere

I like the idea here in the abstract (more than I like GatewayClass) and don't have any specific objections to the content of the GEP, but can agree we should hold off on introducing/requiring a Mesh resource until we have a specific functional need this will unblock.