-
Bug
-
Resolution: Done
-
Major
-
Pipelines 1.6
-
2
-
False
-
False
-
The pod serving the `tkn` CLI will now be scheduled on nodes, based on the node selector and toleration limits specified in the `TektonConfig` custom resource.
-
-
Pipelines Sprint 211
the pod serving the tkn cli is created in openshift addon section and currently we don't pass the config.nodeSelector and config.tolerations to TektonAddon
to fix this, we need to pass both the configurations from TektonConfig to TektonAddon and later use `AddConfiguration` transformer to add in the deployment.
fields example: https://github.com/tektoncd/operator/blob/91460bed88672f6feb6a6dbec11663e74aef9b6a/pkg/apis/operator/v1alpha1/tektonpipeline_types.go#L51