mirror of https://github.com/k3s-io/k3s
4ee877c226
Automatic merge from submit-queue allow handler to join after the informer has started This allows an event handler to join after a SharedInformer has started. It can't add any indexes, but it can add its reaction functions. This works by 1. stopping the flow of events from the reflector (thus stopping updates to our store) 1. registering the new handler 1. sending synthetic "add" events to the new handler only 1. unblocking the flow of events It would be possible to 1. block 1. list 1. add recorder 1. unblock 1. play list to as-yet unregistered handler 1. block 1. remove recorder 1. play recording 1. add new handler 1. unblock But that is considerably more complicated. I'd rather not start there since this ought to be the exception rather than the rule. @wojtek-t who requested this power in the initial review @smarterclayton @liggitt I think this resolves our all-in-one ordering problem. @hongchaodeng since this came up on the call |
||
|---|---|---|
| .. | ||
| daemon | ||
| deployment | ||
| endpoint | ||
| framework | ||
| garbagecollector | ||
| job | ||
| namespace | ||
| node | ||
| petset | ||
| podautoscaler | ||
| podgc | ||
| replicaset | ||
| replication | ||
| resourcequota | ||
| route | ||
| service | ||
| serviceaccount | ||
| volume | ||
| OWNERS | ||
| controller_utils.go | ||
| controller_utils_test.go | ||
| doc.go | ||
| lookup_cache.go | ||