Skip to content

Commit d4c6e2e

Browse files
p3rf Teamcopybara-github
authored andcommitted
Remove waiting for pods after the rollout completes.
The wait takes a long time, and seems to get confused if cluster autoscaler adds/removes nodes and shifts pods around between them. This leads to lengthy tests that eventually fail with a timeout error. Plus, at least in theory, once the rollout completes, we should have the pods and shouldn't have to wait at all... though we suspect this may not always be true. PiperOrigin-RevId: 822736504
1 parent 5fe6d8e commit d4c6e2e

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

perfkitbenchmarker/linux_benchmarks/kubernetes_scale_benchmark.py

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -204,13 +204,6 @@ def ScaleUpPods(
204204
cluster.WaitForRollout(rollout_name, timeout=max_wait_time)
205205

206206
all_new_pods = set(cluster.GetPodNames()) - initial_pods
207-
cluster.WaitForResource(
208-
'pod',
209-
condition_name='Ready',
210-
timeout=max_wait_time,
211-
wait_for_all=True,
212-
namespace='default',
213-
)
214207
end_polling_time = time.monotonic()
215208
logging.info(
216209
'In %d seconds, found all %s new pods',

0 commit comments

Comments
 (0)