SeleniumHQ / SeleniumHQ/docker-selenium
[🚀 Feature]: Gateway API
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
Feature and motivation
Hi, I encountered an issue where WebSocket connections drop during the application of the Nginx configuration, resulting in 502 errors. One potential solution could be migrating to Gateway API. It would be great to add the option to create resources for Gateway API in the chart. For a quick start, you can use ingress2gateway
Usage example
This will permanently resolve the issue with WebSocket disconnections.
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 reviewing the repository's Helm chart and the Gateway API documentation, using ingress2gateway as the suggested reference. Define how the chart should optionally generate Gateway API resources and verify that the resulting configuration addresses WebSocket disconnections during Nginx updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, nginx
- Domain
- devops, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100