github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
47,431 Commits
32 Branches
881 Tags
633 MiB
Commit Graph

59 Commits (a926c1f258ab3aa25de58c4958fbf39b32a08f98)

Author SHA1 Message Date
Harry Zhang c31ec5607a Refactor version cache into kubelet util 2016-04-13 00:42:22 -04:00
laushinka 7ef585be22 Spelling fixes inspired by github.com/client9/misspell 2016-02-18 06:58:05 +07:00
Daniel Smith 4a7d70aef1 extend fake clock 2016-02-01 15:36:15 -08:00
Yu-Ju Hong 4ab505606b Always overwrite items in kubelet's work queue 
This allows kubelet to change the next sync time based on the last result.
 2016-01-12 16:25:19 -08:00
Yu-Ju Hong fda73c04ec Change to include UID by default in formatting 2015-12-07 13:32:02 -08:00
Yu-Ju Hong a4816b3bcb Make kublet/util/format.go a separate package 
The formatting function is used often in logging. This improves the readability
by shortening the length of the call. Also change the fomartted string to
include the pod UID.
 2015-12-03 12:47:36 -08:00
Yu-Ju Hong 2eb17df46b kubelet: independent pod syncs and backoff on error 
Currently kubelet syncs all pods every 10s. This is not preferred because
 * Some pods may have been sync'd recently.
 * This may cause all the pods to be sync'd at once, causing undesirable
   CPU spikes.

This PR replaces the global syncs with independent, periodic pod syncs. At the
end of syncing, each pod worker will enqueue itslef with a future timestamp (
current time + sync interval), when it will be due for another sync.
 * If the pod worker encoutners an sync error, it may requeue with a different
   timestamp to retry sooner.
 * If a sync is triggered by the update channel (events or spec changes), the
   pod worker would enqueue a new sync time.

This change is necessary for moving to long or no periodic sync period once pod
lifecycle event generator is completed. We will still rely on the mechanism to
requeue the pod on sync error.

This change also makes sure that if a sync does not succeed (either due to
real error or the per-container backoff mechanism), an error would be propagated
back to the pod worker, which is responsible for requeuing.
 2015-11-03 13:29:08 -08:00
Mike Danese 8e33cbfa28 rewrite go imports 2015-08-05 17:30:03 -07:00
Yu-Ju Hong f7fd7e9687 Kubelet: add and modify some logging messsages 
This helps debug #6651
 2015-06-24 16:29:19 -07:00