k3s embedded API server and agent watch clients: who owns reconnection timing after a dropped watch?
Where the components meet k3s runs an embedded API server in the server process; each agent watches it through a standard client-go client. They meet at the watch stream: the server side honors context cancellation and closes the stream, while the agent side reconnects using client-go's default exponential backoff, commonly capped near 30 seconds, with the i
k3s
kubernetes
helm