tekton-pipelines namespace. This guide covers all available configuration options.
ConfigMap Overview
Tekton Pipelines uses the following ConfigMaps for configuration:config-defaults- Default values for TaskRuns and PipelineRunsfeature-flags- Feature gates and experimental featuresconfig-events- CloudEvents configurationconfig-observability- Metrics and observability settingsconfig-spire- SPIRE security configurationconfig-leader-election-controller- Leader election settingsconfig-wait-exponential-backoff- Retry backoff configuration
Default Configuration (config-defaults)
Theconfig-defaults ConfigMap controls default values for TaskRuns and PipelineRuns.
Timeout Settings
Default timeout in minutes for TaskRuns and PipelineRuns when none is specified.
Duration to wait before declaring failure when image pull fails with
imagePullBackOff. Setting to "0" enables fail-fast behavior.Service Account
Default service account name for TaskRuns and PipelineRuns when none is specified.
Pod Template
Default pod template applied to all TaskRun pods. Can include node selectors, tolerations, and other pod specifications.
Default pod template for affinity assistant pods.
Workspace Configuration
Default workspace binding for workspaces declared by Tasks but not provided by TaskRuns.
Matrix Configuration
Maximum number of parameter combinations in a Matrix that can be used to fan out a PipelineTask.
Environment Variables
Comma-separated list of environment variables that cannot be overridden by podTemplate.
Labels
Default value for the
app.kubernetes.io/managed-by label applied to all pods created for TaskRuns.Resolver Configuration
Default resolver type to use in the cluster (e.g.,
git, bundles, hub, cluster).Maximum duration for the resolution controller before timing out.
Results Configuration
Polling interval for the sidecar log results container. Controls how frequently the sidecar checks for step completion files.Lower values (e.g.,
10ms) increase responsiveness but may increase CPU usage. Higher values (e.g., 1s) reduce resource usage but may delay result collection.Only applicable when using the sidecar-logs approach for results.
Step Reference Concurrency
Maximum number of concurrent goroutines for resolving step references. Prevents overwhelming remote servers when TaskRuns contain many steps referencing StepActions.
Resource Requirements
Default resource requirements for containers created by the controller.
Feature Flags (feature-flags)
Thefeature-flags ConfigMap controls experimental and beta features.
API Fields
Determines which gated features are enabled. Acceptable values:
stable, beta, alpha.Affinity and Scheduling
Determines how PipelineRun pods are scheduled with Affinity Assistant.
workspaces- Schedule TaskRuns sharing PVC-based workspace to same nodepipelineruns- Schedule all TaskRuns in a PipelineRun to same nodeisolate-pipelinerun- Schedule to same node, only one PipelineRun per nodedisabled- No coschedule policy
Sidecar Configuration
Wait for sidecar containers to be running before starting the first step.Setting to
false allows immediate step execution but may cause issues with Tasks using sidecars.Whether the cluster uses injected sidecars (e.g., Istio). Setting to
false can decrease TaskRun startup time.Enable native Kubernetes sidecar support. Requires Kubernetes v1.29 or greater.
Credentials and Authentication
Disable Tekton’s built-in credential initialization. When enabled, use Workspaces to mount credentials from Secrets.
Require Git SSH Secrets to include a
known_hosts field for server key validation.OCI Bundles
Enable Tekton OCI bundle usage, allowing
bundle field in taskRef and pipelineRef.Results
Method for extracting results from tasks.
termination-message- Use container termination message (4096 byte limit)sidecar-logs- Use sidecar logs (configurable limit, beta feature)
Maximum size in bytes for each result when using
sidecar-logs. Cannot exceed 1.5MB (CRD size limit).Security
Set security context for containers injected by Tekton. Required for running in namespaces with
restricted pod security standards.Enable
readOnlyRootFilesystem in security context. Requires set-security-context to be enabled.Does not work on Windows platforms.
Policy when no matching verification policies are found.
fail- Fail TaskRun/PipelineRun if no matching policies foundwarn- Skip verification and log warningignore- Skip verification silently
Configure non-falsifiable provenance support.
spire- Use SPIRE for non-falsifiable provenance (experimental)none- No non-falsifiable provenance
CloudEvents
Enable CloudEvents for CustomRuns and Runs when a CloudEvents sink is configured.
Provenance
Populate the
provenance field in TaskRun and PipelineRun status with metadata about resources used.Advanced Features
Keep pods running when TaskRuns are cancelled, allowing log examination.
Enable CEL (Common Expression Language) evaluation in WhenExpressions.
Enable built-in parameter input validation via parameter enums.
Prevent users from creating embedded spec TaskRuns or PipelineRuns. Comma-separated list of resource types.
Enable concise resolver syntax for referencing remote resources.
Enable StepActions feature (stable feature, cannot be disabled).
Enable the use of Artifacts in Steps (preview mode, not yet implemented).
Retry Configuration
Enable exponential backoff retry strategy for TaskRun and CustomRun creation on webhook timeouts.Configure backoff parameters in the
config-wait-exponential-backoff ConfigMap.Exponential Backoff Configuration (config-wait-exponential-backoff)
Whenenable-wait-exponential-backoff is enabled, customize retry behavior:
Initial duration before the first retry.
Factor by which duration increases after each retry.
Jitter factor for randomizing retry intervals (0.0 = no jitter, 0.2 = up to 20% additional wait).
Number of backoff steps (retry attempts).
Maximum duration between retries.
Remote Resolvers Configuration
Four remote resolvers are enabled by default and can be disabled in theresolvers-feature-flags ConfigMap:
Registry Certificate Configuration
For private registries with self-signed certificates:SSL_CERT_DIR is set to /etc/ssl/certs by default. If your cert is not in the default directory, configure it using this ConfigMap.