knative-extensions / knative-extensions/net-gateway-api
Resolve HA / multi-thread concerns around Gateway updates
- Dominant language
- Go
- Stars
- 50
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Currenty, we assume a single `Gateway` resource; when using auto-TLS, we need to update `Spec.Listeners` for each Knative Route.
The default controller implementation will attempt to reconcile multiple KIngress resources at once, which means that it's likely that we will get some number of update collisions on the Gateway. We should figure out a mechanism for spreading updates across multiple Gateways to enable HA / multi-threaded controllers without bottlenecking on a single Gateway instance.
This is extracted from [this PR comment](https://github.com/knative-sandbox/net-gateway-api/pull/316#discussion_r908792218)
Contributor guide
Research direction
Start by reviewing the current controller implementation that updates Gateway Spec.Listeners for auto-TLS and the linked PR comment. Determine how concurrent KIngress reconciliation causes Gateway update collisions, then define a mechanism that distributes updates across multiple Gateways without bottlenecking on one instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100