• Yu-Ju Hong's avatar
    kubelet: trigger pod workers independently · b906e345
    Yu-Ju Hong authored
    Currently, whenever there is any update, kubelet would force all pod workers to
    sync again, causing resource contention and hence performance degradation.
    
    This commit flips kubelet to use incremental updates (as opposed to snapshots).
    This allows us to know what pods have changed and send updates to those pod
    workers only. The `SyncPods` function has been replaced with individual
    handlers, each handling an operation (ADD, REMOVE, UPDATE). Pod workers are
    still triggered periodically, and kubelet performs periodic cleanup as well.
    
    This commit also spawns a new goroutine solely responsible for killing pods.
    This is necessary because pod killing could hold up the sync loop for
    indefinitely long amount of time now user can define the graceful termination
    period in the container spec.
    b906e345
Name
Last commit
Last update
Godeps Loading commit data...
api/swagger-spec Loading commit data...
build Loading commit data...
cluster Loading commit data...
cmd Loading commit data...
contrib Loading commit data...
docs Loading commit data...
examples Loading commit data...
hack Loading commit data...
hooks Loading commit data...
pkg Loading commit data...
plugin Loading commit data...
test Loading commit data...
third_party Loading commit data...
www Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
CHANGELOG.md Loading commit data...
CONTRIB.md Loading commit data...
CONTRIBUTING.md Loading commit data...
DESIGN.md Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
Vagrantfile Loading commit data...
logo.pdf Loading commit data...
logo.png Loading commit data...
logo.svg Loading commit data...
logo_usage_guidelines.md Loading commit data...
shippable.yml Loading commit data...