Use information from lease WATCH system to respond to added/removed servers more quickly

[carreter]

PR #643 adds a new lease-based system for detecting the number of servers each agent should be connected to. However, a lease count is only calculated upon a new server connection request.

An improved version of this system would hook into the lease Informer's event system to initiate a new connection when a new lease is detected.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale