Proposed Change
Summary
When a route's options field changes (e.g. loadbalancing strategy) but its identity fields (hostname, protocol, isolation segment, route service URL) stay the same, route-emitter emits nothing — no registration, no unregistration. The updated options only reach gorouter at the next periodic heartbeat cycle, which is 60 seconds.
Expected behaviour
An options-only change should immediately emit one registration with the new options so gorouter picks it up without waiting for the next heartbeat.
Code here:
src/code.cloudfoundry.org/route-emitter/routingtable
Acceptance criteria
As a developer
I want to set route options in CAPI and they appear immediately in go-router
So that I do not have to wait 60s for my changes to be applied
Related links
No response
Proposed Change
Summary
When a route's
optionsfield changes (e.g.loadbalancingstrategy) but its identity fields (hostname, protocol, isolation segment, route service URL) stay the same, route-emitter emits nothing — no registration, no unregistration. The updated options only reach gorouter at the next periodic heartbeat cycle, which is 60 seconds.Expected behaviour
An options-only change should immediately emit one registration with the new options so gorouter picks it up without waiting for the next heartbeat.
Code here:
src/code.cloudfoundry.org/route-emitter/routingtableAcceptance criteria
As a developer
I want to set route options in CAPI and they appear immediately in go-router
So that I do not have to wait 60s for my changes to be applied
Related links
No response