Skip to content

Commit d248469

Browse files
Add Gateway For Mesh section to the GEP template (#3577)
* Add Gateway For Mesh section to the GEP template * Update index.md * Apply suggestions from code review Co-authored-by: Mattia Lavacca <[email protected]> --------- Co-authored-by: Mattia Lavacca <[email protected]>
1 parent 7f18b6d commit d248469

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

geps/gep-696/index.md

+10-1
Original file line numberDiff line numberDiff line change
@@ -24,15 +24,22 @@ the content into the GEP as online documents are easier to lose
2424
-- e.g. owner messes up the permissions, accidental deletion)
2525

2626
## API
27-
2827
(... details, can point to PR with changes)
2928

29+
### Gateway for Ingress (North/South)
30+
(Include API details for North/South usecases)
31+
32+
### Gateway For Mesh (East/West)
33+
(Include East/West API considerations, examples, and if different - APIs)
34+
3035
## Conformance Details
3136

3237
(from https://github.com/kubernetes-sigs/gateway-api/blob/main/geps/gep-2162/index.md#standardize-features-and-conformance-tests-names)
3338

3439
#### Feature Names
3540

41+
(Does it require separate feature(s) for mesh? Please add them if necessary)
42+
3643
Every feature should:
3744

3845
1. Start with the resource name. i.e HTTPRouteXXX
@@ -49,6 +56,8 @@ Treat this guidance as "best effort" because we might have test files that check
4956

5057
In any case, the conformance tests file names should be meaningful and easy to understand.
5158

59+
(Make sure to also include conformance tests that cover mesh)
60+
5261
## Alternatives
5362

5463
(List other design alternatives and why we did not go in that

0 commit comments

Comments
 (0)