As a User, new to the Gateway API, I will likely encounter the community Getting Started guides and use them with a variety of Gateway implementations.
Our implementation must be compatible with these guides. We won’t support every case immediately; the A/C will specifically mention each guide individually. When blocked, specific follow-up stories are expected to be filed to fix and build support.
Note: Eventually these guides should provide a foundation for automated e2e tests.
A/C:
Verify “Deploying a simple Gateway” configurations and walk-through
Verify “HTTP Routing” configurations and walk-through
Verify “HTTP path redirects and rewrites”
Redirects is supported for milestone III
File follow-on feature for rewrites (will link here if filed before this story is assigned)
File follow-on feature for “HTTP traffic splitting” (NKG-70)
Verify “Cross-Namespace routing” configurations and walk-through
Verify “Configuring TLS”. File follow-on features for discovered gaps.
Do not verify “TCP routing”. No feature goals at the time of this submittal.
brianehlert
commented
1 year ago
As a User, new to the Gateway API, I will likely encounter the community Getting Started guides and use them with a variety of Gateway implementations.
Our implementation must be compatible with these guides. We won’t support every case immediately; the A/C will specifically mention each guide individually. When blocked, specific follow-up stories are expected to be filed to fix and build support.
Note: Eventually these guides should provide a foundation for automated e2e tests.
A/C:
Verify “Deploying a simple Gateway” configurations and walk-through
Verify “HTTP Routing” configurations and walk-through
Verify “HTTP path redirects and rewrites”
Redirects is supported for milestone III
File follow-on feature for rewrites (will link here if filed before this story is assigned)
File follow-on feature for “HTTP traffic splitting” (NKG-70)
Verify “Cross-Namespace routing” configurations and walk-through
Verify “Configuring TLS”. File follow-on features for discovered gaps.
Do not verify “TCP routing”. No feature goals at the time of this submittal.