From ced2e65acddbee2e6e9c412cfa6833848b24820c Mon Sep 17 00:00:00 2001 From: Alvaro Aleman Date: Mon, 8 May 2023 15:33:22 -0400 Subject: [PATCH] CA: Add pod namespace when logging why scaleup wasn't possible We have many identical statefulsets in different namespaces, as a result, the pod name by itself is close to useless as an identifier. Add the namespace in the log. --- cluster-autoscaler/core/scaleup/orchestrator/orchestrator.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cluster-autoscaler/core/scaleup/orchestrator/orchestrator.go b/cluster-autoscaler/core/scaleup/orchestrator/orchestrator.go index b851a9e599..11394261ce 100644 --- a/cluster-autoscaler/core/scaleup/orchestrator/orchestrator.go +++ b/cluster-autoscaler/core/scaleup/orchestrator/orchestrator.go @@ -472,7 +472,7 @@ func (o *ScaleUpOrchestrator) SchedulablePods( // Mark pod group as (theoretically) schedulable. eg.Schedulable = true } else { - klog.V(2).Infof("Pod %s can't be scheduled on %s, predicate checking error: %v", samplePod.Name, nodeGroup.Id(), err.VerboseMessage()) + klog.V(2).Infof("Pod %s/%s can't be scheduled on %s, predicate checking error: %v", samplePod.Namespace, samplePod.Name, nodeGroup.Id(), err.VerboseMessage()) if podCount := len(eg.Pods); podCount > 1 { klog.V(2).Infof("%d other pods similar to %s can't be scheduled on %s", podCount-1, samplePod.Name, nodeGroup.Id()) }