search

cloud-bulldozer / benchmark-operator

The Chuck Norris of cloud benchmarks
Apache License 2.0
282 stars 128 forks source link

[Uperf] NodePort servicetype does not work with pairs > 1 #757

Closed smalleni closed 2 years ago

smalleni commented 2 years ago

Describe the bug When running the uperf workload with a servicetype of NodePort, we are only able to run it with one pair of client/servers. Running it with greater than 1 pairs results in port conflicts since the service ports of different servers are exposed as NodePorts with the same port numbers .

To Reproduce Steps to reproduce the behavior:

  1. Run uperf workload with servicetype of NodePort and pairs > 1

Expected behavior The test should work and report results like it does for servicetype clusterip

Actual behavior

   "msg": "Failed to create object: b'{\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"Service \\\\\"uperf-service-1-0b7f94a7\\\\\" is invalid: spec.ports[0].nodePort: Invalid value: 30000: provided port is already allocated\",\"reason\":\"Invalid\",\"details\":{\"name\":\"uperf-service-1-0b7f94a7\",\"kind\":\"Service\",\"causes\":[{\"reason\":\"FieldValueInvalid\",\"message\":\"Invalid value: 30000: provided port is already allocated\",\"field\":\"spec.ports[0].nodePort\"}]},\"code\":422}\\n'",
    "reason": "Unprocessable Entity",