Maestro is not behaving as expected when it chooses a hostPort that is not available in any of the kubernetes nodes, in this cases it should edit the pod to change the chosen hostPort or delete it and create a new one to trigger another random port get
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 49s (x26 over 8m) default-scheduler 0/10 nodes are available: 1 Insufficient cpu, 1 PodFitsHostPorts, 1 PodToleratesNodeTaints, 9 MatchNodeSelector.
Maestro is not behaving as expected when it chooses a hostPort that is not available in any of the kubernetes nodes, in this cases it should edit the pod to change the chosen hostPort or delete it and create a new one to trigger another random port get