cloud-bulldozer / cloud-bulldozer/e2e-benchmarking
Exclude NotReady nodes from Node Count
- Dominant language
- Shell
- Stars
- 45
- Forks
- 85
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
When generating the number of pods to create and labeling the nodes, we should exclude NotReady nodes, to avoid generating a number of pods higher to number of schedulable pods
ip-10-0-210-139.us-west-2.compute.internal NotReady,SchedulingDisabled worker 57m v1.23.5+b0357ed
lun 28 mar 2022 12:03:17 UTC Labeling 27 worker nodes with node-density=enabled
[...]
node/ip-10-0-210-139.us-west-2.compute.internal labeled
[...]
lun 28 mar 2022 12:03:47 UTC ###############################################
lun 28 mar 2022 12:03:47 UTC Workload: node-density
lun 28 mar 2022 12:03:47 UTC Workload template: workloads/node-pod-density/node-pod-density.yml
lun 28 mar 2022 12:03:47 UTC Metrics profile: metrics-profiles/metrics.yaml
lun 28 mar 2022 12:03:47 UTC Alerts profile:
lun 28 mar 2022 12:03:47 UTC QPS: 20
lun 28 mar 2022 12:03:47 UTC Burst: 20
lun 28 mar 2022 12:03:47 UTC Node count: 27
lun 28 mar 2022 12:03:47 UTC Pods per node: 245
lun 28 mar 2022 12:03:47 UTC ###############################################
lun 28 mar 2022 12:03:17 UTC Number of pods to deploy on nodes: 6181
Node count should be 26, not 27
https://github.com/cloud-bulldozer/e2e-benchmarking/blob/86c18427a5004a37e4a3a911fba262f4719ee867/workloads/kube-burner/common.sh#L81
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.