5 Commits

Author	SHA1	Message	Date
WanLinghao	7df1078d6f	Currently, kubelet token mamanger only clean tokens who are expired. For tokens with long expiration, if the pod who creates them got killed or evicted, those tokens may stay in kubelet's memory until they are expired. It's bad for kubelet and node itself. After this patch, each time a pod was deleted, token manager would clean related tokens.	2018-10-22 09:32:59 +08:00
WanLinghao	794e665d7b	Currently, token manager use keyFunc like: fmt.Sprintf("%q/%q/%#v", name, namespace, tr.Spec). ... Since tr.Spec contains point fields, new token request would not reuse the cache at all. This patch fix this, also adds unit test. Signed-off-by: Mike Danese <mikedanese@google.com>	2018-09-06 09:03:26 -07:00
WanLinghao	52140ea1d3	fix a bug of wrong parameters which could cause token projection failure	2018-06-08 12:00:58 +08:00
Mike Danese	90ba15ee74	auth: standalone kubelets shouldn't start a token manager	2018-06-05 17:31:26 -07:00
Mike Danese	91feb345aa	implement service account token projection	2018-06-04 17:22:08 -07:00