Kube-burner's node-density uses the number of worker nodes to calculate the number of pods to deploy in the cluster.
With this change recently pushed, kube-burner's failes because the nodes in the CI cluster has the scheduler configured with mastersSchedulable: true, hence the nodes are labeled as master and workers simultaneosly
Kube-burner's node-density uses the number of worker nodes to calculate the number of pods to deploy in the cluster. With this change recently pushed, kube-burner's failes because the nodes in the CI cluster has the scheduler configured with
mastersSchedulable: true, hence the nodes are labeled as master and workers simultaneoslyhttps://github.com/cloud-bulldozer/go-commons/blob/97b61546de4fd5673e10ba17005fa01c01b13036/ocp-metadata/ocp-metadata.go#L215-L226
We should fix this corner case.