In many cases - the default out of the box harness functionality is close to desirable behaviours, but needs augmenting to make it useful / work in a given ecosystem - especially when you execute CI steps on self hosted kubernetes.

Things like security restrictions / proxy configuration etc often need augmented containers to be able to work correctly. So - in many cases clients like this are forced to replicate out of the box behaviours rather than embrace and extend the default.

Hey Navy Horse

Thanks for the feature request. Could you please elaborate more on this request and why it is important to you? Specifically, could you let me know what "should be open to extension and allow the users to customize behaviors" mean? Alternatively, we could get on a call if required.

Thanks,

Abhishek Thamman