You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Propagate NodeSelector and Tolerations to Affinity Assistant
To be able to run Tekton workload on a subset of the Nodes in a cluster,
a NodeSelector or Tolerations can be set on the pods, e.g. by specifying a
custom PodTemplate.
When using the Affinity Assistant, this was not supported to customize.
This commit, also propagate NodeSelector and Tolerations to the Affinity Assistant pod,
so that Tekton workload can be kept to a subset of the Nodes in a cluster, also when
using the Affinity Assistant.
Fixes#2742
/kind feature
Copy file name to clipboardExpand all lines: docs/install.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -245,7 +245,7 @@ The example below customizes the following:
245
245
- the default timeout from 60 minutes to 20 minutes.
246
246
- the default `app.kubernetes.io/managed-by` label is applied to all Pods created to execute `TaskRuns`.
247
247
- the default Pod template to include a node selector to select the node where the Pod will be scheduled by default.
248
-
For more information, see [`PodTemplate` in `TaskRuns`](./taskruns.md#pod-template) or [`PodTemplate` in `PipelineRuns`](./pipelineruns.md#pod-template).
248
+
For more information, see [`PodTemplate` in `TaskRuns`](./taskruns.md#specifying-a-pod-template) or [`PodTemplate` in `PipelineRuns`](./pipelineruns.md#specifying-a-pod-template).
0 commit comments