☔ Gateway API - `TLSRoute` extended conformance
Open
area/conformance
area/gateway-api
epic
stale
- Dominant language
- Go
- Stars
- 109
- Forks
- 49
- Avg merge
- 21h 28m
- Merged PRs (30d)
- 313
Description
## Problem Statement
This issue is the umbrella for all the issues related to `HTTPRoute` extended conformance in Gateway API.
## Additional information
This is intended to be a long-living issue: as long as new tests get added upstream, this umbrella issue should be updated accordingly.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named in the issue, so start by identifying the upstream Gateway API conformance tests covered by this umbrella. Reconcile the title's TLSRoute scope with the body’s HTTPRoute wording, then update the issue as new upstream tests are added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- api, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100