mirror of https://github.com/linkerd/linkerd2.git
3902b339e7
We the destination controller's workload watcher receives an update for any Server resource, it recomputes opaqueness for every workload. This is because the Server update may have changed opaqueness for that workload. However, this is very CPU intensive for the destination controller, especially during resyncs when we get Server updates for every Server resource in the cluster. Instead, we only need to recompute opaqueness for workloads that are selected by the old version of the Server or by the new version of the Server. If a workload is not selected by either the new or old version of the Server, then the Server update cannot have changed the workload's opaqueness. Signed-off-by: Alex Leong <alex@buoyant.io> |
||
|---|---|---|
| .. | ||
| cluster_store.go | ||
| cluster_store_test.go | ||
| endpoints_watcher.go | ||
| endpoints_watcher_test.go | ||
| k8s.go | ||
| opaque_ports_watcher.go | ||
| opaque_ports_watcher_test.go | ||
| profile_watcher.go | ||
| profile_watcher_test.go | ||
| prometheus.go | ||
| test_util.go | ||
| workload_watcher.go | ||
| workload_watcher_test.go | ||