mirror of
				https://github.com/optim-enterprises-bv/kubernetes.git
				synced 2025-11-03 19:58:17 +00:00 
			
		
		
		
	Merge pull request #60579 from gmarek/ss_logs
Automatic merge from submit-queue (batch tested with PRs 61118, 60579). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Increase loging verbosity for deleting stateful set pods We should always log reasons for deleting StatefulSet Pods. @jdumars - what's the current process for putting such changes into the release? It's literally 0-risk change that helps with debugging. cc @ttz21 ```release-note NONE ```
This commit is contained in:
		@@ -469,7 +469,7 @@ func (ssc *defaultStatefulSetControl) updateStatefulSet(
 | 
			
		||||
				firstUnhealthyPod.Name)
 | 
			
		||||
			return &status, nil
 | 
			
		||||
		}
 | 
			
		||||
		glog.V(4).Infof("StatefulSet %s/%s terminating Pod %s for scale dowm",
 | 
			
		||||
		glog.V(2).Infof("StatefulSet %s/%s terminating Pod %s for scale dowm",
 | 
			
		||||
			set.Namespace,
 | 
			
		||||
			set.Name,
 | 
			
		||||
			condemned[target].Name)
 | 
			
		||||
@@ -502,7 +502,7 @@ func (ssc *defaultStatefulSetControl) updateStatefulSet(
 | 
			
		||||
 | 
			
		||||
		// delete the Pod if it is not already terminating and does not match the update revision.
 | 
			
		||||
		if getPodRevision(replicas[target]) != updateRevision.Name && !isTerminating(replicas[target]) {
 | 
			
		||||
			glog.V(4).Infof("StatefulSet %s/%s terminating Pod %s for update",
 | 
			
		||||
			glog.V(2).Infof("StatefulSet %s/%s terminating Pod %s for update",
 | 
			
		||||
				set.Namespace,
 | 
			
		||||
				set.Name,
 | 
			
		||||
				replicas[target].Name)
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user