RELEASED: Public: September 8, 2022
Resolved issues
- Reduced the number of HTTP connections allocated to Kubernetes watches (BEE-1187)
-
A large number of HTTP connections were opened for watching Kubernetes events. This lead to performance issues when an environment had a large number of controllers.
A single watcher is now added for each namespace, reducing the number of allocated HTTP connections for watching events.
- Redesigned usage of Kubernetes clients in controller provisioning plugin (BEE-20348)
-
The existing design suffered from scaling issues, leaving idle threads behind. The new design ensures threads are reused as needed, and only a limited number of threads is created for each declared cluster endpoint.