Missing support for ListenerSet
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Description of the change
The gateway API supports the concept of a ListenerSet that better supports a multi-tenant gateway, but the Nextcloud helm chart only supports HTTPRoutes.
Benefits
Adding support for ListenerSet means this chart supports shared gateways. Without this support, users in this situation must deploy a ListenerSet manually. This isn't a huge deal, but it does make deployment more complex.
Possible drawbacks
One more thing for the chart to manage and get bugs logged against.
Additional information
If there is an appetite for this, I'd be happy to propose a PR.
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 Gateway API ListenerSet guide and tracing how the chart currently configures HTTPRoutes. Identify the existing values and rendered templates involved, then verify that a configured ListenerSet renders correctly alongside the chart's gateway resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100