Gateway API support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 191
- Forks
- 98
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
The chart currently only exposes Qdrant via Ingress.
The Gateway API is now GA. The core resources (Gateway and HTTPRoute) graduated to v1 / GA with the Gateway API v1.0 release in October 2023, and it is widely adopted as the successor to Ingress across implementations (Traefik, Istio, Contour, Cilium, NGINX Gateway Fabric, and others).
Are there plans to support it in the chart? For example, an opt-in HTTPRoute (and GRPCRoute) template alongside the existing Ingress.
Would be great to have it supported going forward.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the chart's existing Ingress template and the configuration that controls exposure. Confirm the desired opt-in behavior and Gateway API v1 resources with maintainers; done means the chart can render an optional HTTPRoute, and possibly GRPCRoute, alongside Ingress without changing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100