mirror of https://github.com/k3s-io/k3s
![]() This should ensure all load balancers get deleted even if a reordering of watch events causes us to strand one after its service has been deleted, because the sync will notice that the service controller's cache has a service in it that no longer exists in the apiserver. It could still leak in the case that the controller manager is killed between when it leaks something and the sync runs, but this should improve things. |
||
---|---|---|
.. | ||
kubernetes.go |