Feature Request - Set global node selector for pods
long-term
T
Theoretical Vole
It would be useful if we could set a node selector or tolerations for Harness pods. I know this can be done at the pipeline level, but I would like to be able to do this globally, perhaps at the Kubernetes connector level.
So we would be able to set a default node selector and toleration, but if one has been set at the pipeline level this would override the default.
This would apply to delegates and to pods created by pipelines.
Log In
Canny AI
Merged in a post:
Capability to add K8s toleration, affinity and annotation to all pods that are created by harness during CI/CD pipeline execution at global level?
D
Dew Orangutan
We are looking for something that we can be set at global level that adds desired and default toleration, Affinity and annotation to all generated pods by harness.
Pipeline level is not good option, since it is managed by application teams.
Canny AI
Merged in a post:
management of tolerances by the delegate
G
Gold Crab
Hello,
I would also like to suggest the implementation of a feature where tolerances are either maintained or managed by the delegate, eliminating the need to specify them at the pipeline level.
Recently, I had to modify 9 pipelines across different services to support new tolerances at the Kubernetes level. For example, transitioning to using Azure VMs spot instances for CI execution. The objective of the pipeline itself remained unchanged, but the infrastructure on which they are executed has evolved. Therefore, it seems unnecessary to require alterations at the pipeline level for such infrastructure changes.
Best Regards,
Miraldo Ramos
N
Nofar Bluestein
.
D
Denim Armadillo
Pranav Rastogi Could you please look into the above feature request.
Pranav Rastogi
long-term
Pranav Rastogi
under review