When updating the IngressRequestRateLimiterBurstCapacity, it is unnecessarily reread from its atomic storage. We should instead use the value that has already been read.
Unecessary reload of IngressRequestRateLimiterBurstCapacitySecs on update
- Assignee:
-
Patrick Freed
- Reporter:
-
Patrick Freed
- Votes:
-
0 Vote for this issue - Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: