Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Gateway For Mesh section to the GEP template #3577

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion geps/gep-696/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,15 +24,22 @@ the content into the GEP as online documents are easier to lose
-- e.g. owner messes up the permissions, accidental deletion)

## API

(... details, can point to PR with changes)

### Gateway for Ingress (North/South)
(Include API details for North/South usecases)

### Gateway For Mesh (East/West)
(Include East/West API considerations, examples, and if differnet - apis)

## Conformance Details

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

#### Feature Names

(Does it require seperate feature name for mesh? Please add it if necessary)

Every feature should:

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

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

(MAKE sure to also include conformance tests that covers mesh)

## Alternatives

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