18f43e4120
If MaxSurge is set, the controller will attempt to double up nodes up to the allowed limit with a new pod, and then when the most recent (by hash) pod is ready, trigger deletion on the old pod. If the old pod goes unready before the new pod is ready, the old pod is immediately deleted. If an old pod goes unready before a new pod is placed on that node, a new pod is immediately added for that node even past the MaxSurge limit. The backoff clock is used consistently throughout the daemonset controller as an injectable clock for the purposes of testing. |
||
|---|---|---|
| .. | ||
| config | ||
| util | ||
| daemon_controller_test.go | ||
| daemon_controller.go | ||
| doc.go | ||
| init_test.go | ||
| OWNERS | ||
| update_test.go | ||
| update.go | ||