Two steps with different execution conditions can not be executed at the same time because of some input toggle value. Yet the pipeline stage pod created in our Kubernetes cluster included the two steps and summed the cpu & memory limit resources requesting a hug amount of CPUs and memory.

It seems that the Harness CI engine can not evaluate the step execution conditions and so on determine the steps execution path during initialization phase, especially if the execution conditions. include variables values by input set choices.