Merge pull request #42111 from feiskyer/sandbox

Automatic merge from submit-queue (batch tested with PRs 41116, 41804, 42104, 42111, 42120) Remove SandboxReceived event This PR removes SandboxReceived event in sync pod. > This event seems somewhat meaningless, and clouds the event records for a pod. Do we actually need it? Pulling and pod received on the node are very relevant, this seems much less so. Would suggest we either remove it, or turn it into a message that clearly indicates why it has value. Refer https://github.com/kubernetes/kubernetes/commit/d65309399a228bd0c085f5e0d1ce93d558aebfaa#commitcomment-21052453. cc @smarterclayton @yujuhong

Merge pull request #42111 from feiskyer/sandbox
be724ba3 · Kubernetes Submit Queue · GitHub · 080a9319 · 245dad86 · be724ba3
Commit be724ba3 authored Feb 27, 2017 by Kubernetes Submit Queue Committed by GitHub Feb 27, 2017
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 2 deletions

kuberuntime_manager.go pkg/kubelet/kuberuntime/kuberuntime_manager.go +1 -2

No files found.
--- a/pkg/kubelet/kuberuntime/kuberuntime_manager.go
+++ b/pkg/kubelet/kuberuntime/kuberuntime_manager.go
@@ -555,9 +555,8 @@ func (m *kubeGenericRuntimeManager) SyncPod(pod *v1.Pod, _ v1.PodStatus, podStat
 		if podContainerChanges.SandboxID != "" {
 			m.recorder.Eventf(ref, v1.EventTypeNormal, "SandboxChanged", "Pod sandbox changed, it will be killed and re-created.")
 		} else {
-			m.recorder.Eventf(ref, v1.EventTypeNormal, "SandboxReceived", "Pod sandbox received, it will be created.")
+			glog.V(4).Infof("SyncPod received new pod %q, will create a new sandbox for it", format.Pod(pod))
 		}
-
 	}

 	// Step 2: Kill the pod if the sandbox has changed.