Kuadrant / Kuadrant/architecture
Support for alternative Gateway API implementations
- Dominant language
- No language data
- Stars
- 3
- Forks
- 16
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 2
Description
We are working on a new Gateway API implementation, and are interested in integrating it with Kuadrant. Reviewing the Kuadrant architecture and documentation, it appears to be tightly coupled to Envoy Gateway/Proxy as the Gateway API implementation.
Is there a roadmap for Kuadrant to support a "bring your own Gateway API implementation" approach to policy enforcement in Kubernetes?
Contributor guide
Research direction
Start by reviewing the Kuadrant architecture and documentation referenced in the issue, focusing on how they depend on Envoy Gateway/Proxy. Determine whether supporting alternative Gateway API implementations is feasible and document a roadmap or decision for a bring-your-own implementation approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100