5 Commits (04575f01b0426f8494d17dc85d47200fcdef3a5e)

Author	SHA1	Message	Date
Davanum Srinivas	954996e231	Move from glog to klog ... - Move from the old github.com/golang/glog to k8s.io/klog - klog as explicit InitFlags() so we add them as necessary - we update the other repositories that we vendor that made a similar change from glog to klog * github.com/kubernetes/repo-infra * k8s.io/gengo/ * k8s.io/kube-openapi/ * github.com/google/cadvisor - Entirely remove all references to glog - Fix some tests by explicit InitFlags in their init() methods Change-Id: I92db545ff36fcec83afe98f550c9e630098b3135	2018-11-10 07:50:31 -05:00
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
Jeff Grafton	23ceebac22	Run hack/update-bazel.sh	2018-06-22 16:22:57 -07: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