content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
Determines whether services in the Pod's namespace are exposed as environment variables to the Pod, similarly to Docker service links. | | `priorityClassName` | Specifies the [priority class](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/) for the Pod. Allows you to selectively enable preemp... | https://github.com/tektoncd/pipeline/blob/main/docs/podtemplates.md | main | tekton | [
-0.014539803378283978,
0.009250796400010586,
0.07305643707513809,
0.03377072885632515,
0.026618393138051033,
-0.02026805840432644,
-0.028804810717701912,
-0.05064065754413605,
0.04571663215756416,
0.021092195063829422,
-0.025455938652157784,
-0.0053779250010848045,
-0.009802224114537239,
0... | 0.16187 |
# Tekton Pipeline Remote Resolution Remote Resolution is a Tekton beta feature that allows users to fetch tasks and pipelines from remote sources outside the cluster. Tekton provides a few built-in resolvers that can fetch from git repositories, OCI registries etc as well as a framework for writing custom resolvers. Re... | https://github.com/tektoncd/pipeline/blob/main/docs/resolution.md | main | tekton | [
-0.06936328858137131,
0.0029555126093328,
-0.00742398900911212,
-0.02877647429704666,
-0.0577363520860672,
-0.09994766116142273,
-0.0984104722738266,
0.09510976076126099,
-0.008954277262091637,
0.07555868476629257,
-0.04935869202017784,
-0.022228797897696495,
-0.012313972227275372,
0.01224... | 0.085538 |
# Bundles Resolver ## Resolver Type This Resolver responds to type `bundles`. ## Parameters | Param Name | Description | Example Value | |------------------|-------------------------------------------------------------------------------|------------------------------------------------------------| | `secret` | The name... | https://github.com/tektoncd/pipeline/blob/main/docs/bundle-resolver.md | main | tekton | [
-0.16591279208660126,
0.04348517954349518,
-0.024345559999346733,
-0.03225741535425186,
-0.08633534610271454,
0.00971485860645771,
0.017669014632701874,
0.10617568343877792,
-0.08095908910036087,
-0.003785174572840333,
0.07587016373872757,
-0.08161216229200363,
0.006770646199584007,
0.0619... | 0.04034 |
Example: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: bundleresolver-config namespace: tekton-pipelines-resolvers data: default-cache-mode: "always" # Always cache unless task/pipeline specifies otherwise ``` ## Usage ### Task Resolution ```yaml apiVersion: tekton.dev/v1beta1 kind: TaskRun metadata: name: rem... | https://github.com/tektoncd/pipeline/blob/main/docs/bundle-resolver.md | main | tekton | [
-0.024723246693611145,
-0.014157119207084179,
-0.02159433253109455,
-0.04874289035797119,
-0.04768475890159607,
-0.06535889208316803,
-0.05481303855776787,
0.007363738026469946,
-0.005492705851793289,
0.05030718073248863,
-0.0015186701202765107,
-0.0763593465089798,
-0.06081251800060272,
0... | 0.005113 |
# Hub Resolver Use resolver type `hub`. ## Parameters | Param Name | Description | Example Value | |------------------|-------------------------------------------------------------------------------|------------------------------------------------------------| | `catalog` | The catalog from where to pull the resource (... | https://github.com/tektoncd/pipeline/blob/main/docs/hub-resolver.md | main | tekton | [
0.012339821085333824,
0.01710321195423603,
-0.03659238666296005,
0.026896130293607712,
-0.04375827684998512,
-0.0008449028246104717,
-0.0393698513507843,
0.031880028545856476,
-0.06631534546613693,
-0.04245317354798317,
-0.02335551381111145,
-0.10912439972162247,
-0.007421684451401234,
0.0... | 0.046314 |
```yaml env - name: ARTIFACT\_HUB\_API value: "https://artifacthub.io/" ``` When setting the `type` field to `tekton`, the resolver will hit the public tekton catalog api at https://api.hub.tekton.dev by default but you can configure your own instance of the Tekton Hub by setting the `TEKTON\_HUB\_API` environment vari... | https://github.com/tektoncd/pipeline/blob/main/docs/hub-resolver.md | main | tekton | [
-0.027840811759233475,
0.038255494087934494,
0.007234465330839157,
-0.02834249474108219,
-0.018757309764623642,
-0.06710617244243622,
-0.08510178327560425,
0.010226991027593613,
0.020459264516830444,
0.03440706804394722,
-0.010722310282289982,
-0.09474949538707733,
0.026746435090899467,
0.... | 0.036589 |
is greater than version `0.7.0` and less than version `2.0.0`, so if the latest task is the version `0.9.0` it will be selected. Other operators for selection are available for comparisons, see the [go-version](https://github.com/hashicorp/go-version/blob/644291d14038339745c2d883a1a114488e30b702/constraint.go#L40C2-L48... | https://github.com/tektoncd/pipeline/blob/main/docs/hub-resolver.md | main | tekton | [
0.000621416955254972,
0.010543220676481724,
-0.005543807987123728,
-0.01990310288965702,
0.10320908576250076,
-0.025372151285409927,
-0.03570666164159775,
-0.025301557034254074,
0.006003355607390404,
0.004137218464165926,
0.04798812046647072,
0.036571744829416275,
-0.05053259804844856,
0.0... | 0.040419 |
# Tekton Pipelines Tekton Pipelines is a Kubernetes extension that installs and runs on your Kubernetes cluster. It defines a set of Kubernetes [Custom Resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that act as building blocks from which you can assemble CI/CD pipeline... | https://github.com/tektoncd/pipeline/blob/main/docs/README.md | main | tekton | [
-0.054844751954078674,
0.020373566076159477,
-0.03762029483914375,
-0.019841976463794708,
-0.030725955963134766,
-0.04467898607254028,
-0.03044297732412815,
0.034827038645744324,
0.11042878031730652,
0.019253509119153023,
-0.03837946802377701,
-0.10362113267183304,
-0.03336774557828903,
-0... | 0.276564 |
# Tasks - [Overview](#overview) - [Configuring a `Task`](#configuring-a-task) - [Defining `Steps`](#defining-steps) - [Reserved directories](#reserved-directories) - [Running scripts within `Steps`](#running-scripts-within-steps) - [Windows scripts](#windows-scripts) - [Specifying a timeout](#specifying-a-timeout) - [S... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.0674595981836319,
0.020037854090332985,
-0.04792574420571327,
0.055579591542482376,
0.03298071026802063,
0.028477758169174194,
-0.0158220361918211,
0.06830114871263504,
-0.04362674430012703,
-0.005037444178014994,
-0.016896286979317665,
-0.02630172111093998,
0.045057885348796844,
-0.032... | 0.020086 |
a reference to a container image that executes a specific tool on a specific input and produces a specific output. To add `Steps` to a `Task` you define a `steps` field (required) containing a list of desired `Steps`. The order in which the `Steps` appear in this list is the order in which they will execute. The follow... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.05350150913000107,
0.07309208065271378,
0.015357955358922482,
-0.026674766093492508,
-0.006651012226939201,
-0.0370413102209568,
-0.013130171224474907,
-0.002673196839168668,
0.06420443207025528,
0.010329149663448334,
-0.04478923976421356,
-0.02415027841925621,
0.022784078493714333,
-0.... | 0.181461 |
steps: - image: my-image # contains /bin/my-binary script: | #!/usr/bin/env bash /bin/my-binary ``` ##### Windows scripts Scripts in tasks that will eventually run on windows nodes need a custom shebang line, so that Tekton knows how to run the script. The format of the shebang line is: `#!win ` Unlike linux, we need t... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.012153233401477337,
0.0489104762673378,
-0.09033684432506561,
0.010250023566186428,
0.023432811722159386,
-0.0074012563563883305,
0.010319535620510578,
0.05841396749019623,
0.012111706659197807,
0.07674040645360947,
-0.03353068605065346,
-0.0899188444018364,
0.02295621857047081,
0.01145... | 0.042302 |
"All Steps have completed executing", "reason": "Succeeded", "status": "True", "type": "Succeeded" } ], "steps": [ { "container": "step-ignore-unit-test-failure", "imageID": "...", "name": "ignore-unit-test-failure", "terminated": { "containerID": "...", "exitCode": 1, "reason": "Completed", } }, ], ``` For an end-to-e... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
0.01938030496239662,
0.05345725640654564,
-0.0024776714853942394,
0.05061393603682518,
0.06028817594051361,
-0.015550279058516026,
-0.04518948867917061,
0.013686959631741047,
0.02991534397006035,
-0.023167099803686142,
-0.02079097181558609,
-0.03517816588282585,
-0.005173938814550638,
0.00... | 0.018242 |
/data - name: parse-project-id image: imega/jq args: - -r - .name - /data/boskosctl-stdout stdoutConfig: path: $(results.project-id.path) volumeMounts: - name: data mountPath: /data volumes: - name: data ``` > NOTE: > > - If the intent is to share output between `Step`s via a file, the user must ensure that the paths p... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
0.0021940029691904783,
0.006063734646886587,
0.01705062761902809,
0.008367104455828667,
0.018565412610769272,
-0.08036911487579346,
-0.04608545079827309,
0.08651690930128098,
0.030644923448562622,
-0.0348360501229763,
-0.025378596037626266,
-0.003337633330374956,
0.018081756308674812,
0.02... | 0.015115 |
workspaces: - name: custom ``` The StepState for a skipped step looks like something similar to the below: ```yaml { "container": "step-run-based-on-step-results", "imageID": "docker.io/library/alpine@sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b", "name": "run-based-on-step-results", "termina... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.06044735014438629,
0.06697610020637512,
-0.012565876357257366,
0.012136447243392467,
0.019752398133277893,
-0.008968902751803398,
-0.0312411580234766,
-0.02035728096961975,
0.02701338566839695,
-0.015407600440084934,
-0.050061341375112534,
-0.048956919461488724,
0.013164252042770386,
-0... | 0.034157 |
defined by setting `type` to `array`. Also, `array` params only supports `string` array i.e. each array element has to be of type `string`. ```yaml spec: params: - name: flags type: array ``` ##### `string` type If not specified, the `type` field defaults to `string`. When the actual parameter value is supplied, its pa... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.0150985699146986,
0.007958182133734226,
-0.08798571676015854,
0.04623439908027649,
-0.0786425992846489,
-0.052318982779979706,
0.1004580706357956,
-0.005584151484072208,
0.013013122603297234,
-0.012999948114156723,
-0.048364970833063126,
0.01757875829935074,
0.009717635810375214,
0.0357... | 0.131656 |
To define a `Task's` results, use the `results` field. In the example below, the `Task` specifies two files in the `results` field: `current-date-unix-timestamp` and `current-date-human-readable`. ```yaml apiVersion: tekton.dev/v1 # or tekton.dev/v1beta1 kind: Task metadata: name: print-date annotations: description: |... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.027202419936656952,
0.07709069550037384,
-0.08426409959793091,
0.0359678640961647,
0.021270958706736565,
0.0032970840111374855,
-0.04689915105700493,
0.08425965905189514,
0.007113595027476549,
0.038085971027612686,
-0.027525020763278008,
-0.06103195995092392,
0.01635861024260521,
0.0220... | 0.072089 |
`string`. Emitting a task result of type `array` is a `beta` feature implemented based on the [TEP-0076](https://github.com/tektoncd/community/blob/main/teps/0076-array-result-types.md#emitting-array-results). You can initialize `array` results from a `task` using JSON escaped string, for example, to assign the followi... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
0.02964216284453869,
0.06994472444057465,
-0.018542610108852386,
0.029571108520030975,
-0.07062036544084549,
-0.05544053018093109,
0.03498263284564018,
-0.03564092889428139,
0.017969535663723946,
-0.006194859743118286,
-0.0405169315636158,
-0.029208563268184662,
-0.000733325956389308,
0.10... | 0.132695 |
more containers we have in our pod, \*the smaller the allowed size of each container's message\*, meaning that the \*\*more steps you have in a Task, the smaller the result for each step can be\*\*. For example, if you have 10 steps, the size of each step's Result will have a maximum of less than 1KB. If your `Task` wr... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.010005968622863293,
0.0692705363035202,
-0.017013248056173325,
-0.02577725239098072,
-0.01292539481073618,
-0.08556050062179565,
-0.04881148040294647,
0.07227780669927597,
0.014831381849944592,
0.04461345821619034,
-0.07920342683792114,
-0.021129336208105087,
-0.025249863043427467,
0.00... | 0.131125 |
the `Steps` in your `Task`. Individual configurations specified within `Steps` supersede the template wherever overlap occurs. In the example below, the `Task` specifies a `stepTemplate` field with the environment variable `FOO` set to `bar`. The first `Step` in the `Task` uses that value for `FOO`, but the second `Ste... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.050819143652915955,
0.04759969934821129,
0.009417117573320866,
0.015528232790529728,
-0.031570933759212494,
0.043592922389507294,
-0.01826724223792553,
0.0274610947817564,
0.005430759862065315,
0.0009441878064535558,
-0.020014779642224312,
-0.0008220048039220273,
-0.018294624984264374,
... | -0.006664 |
- string replacement is performed by the Tekton Controller when a TaskRun is executed. `Tasks` allow you to substitute variable names for the following entities: - [Parameters and resources](#using-variable-substitution) - [`Array` parameters](#using-variable-substitution) - [`Workspaces`](#using-variable-substitution)... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.0015678969211876392,
0.044353507459163666,
-0.05323127284646034,
0.026340875774621964,
-0.03819982707500458,
-0.017516635358333588,
0.08319254219532013,
0.00997820682823658,
-0.0184228103607893,
0.01790829375386238,
-0.03540373593568802,
-0.044782768934965134,
0.08204995840787888,
0.026... | 0.052307 |
string description: name of the secret holding the github-token default: github-token workspaces: - name: source steps: - name: release image: goreleaser/goreleaser workingDir: $(workspaces.source.path)/$(params.package) command: - goreleaser args: - release env: - name: GOPATH value: /workspace - name: GITHUB\_TOKEN v... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.0013553714379668236,
-0.018984558060765266,
-0.024607058614492416,
0.0306316576898098,
0.05674637481570244,
-0.0568208284676075,
0.009693239815533161,
0.023912135511636734,
0.07568203657865524,
0.04296020418405533,
0.05295544117689133,
-0.09381861239671707,
0.039650946855545044,
0.00967... | 0.133995 |
or tekton.dev/v1beta1 kind: Task metadata: name: show-non-root-steps spec: steps: # no securityContext specified so will use # securityContext from TaskRun podTemplate - name: show-user-1001 image: ubuntu command: - ps args: - "aux" # securityContext specified so will run as # user 2000 instead of 1001 - name: show-use... | https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md | main | tekton | [
-0.027654806151986122,
0.020754363387823105,
-0.11023350805044174,
-0.05036716163158417,
0.006841991096735001,
-0.00952480360865593,
0.041823726147413254,
0.11946184188127518,
0.0024242806248366833,
0.04500390589237213,
-0.004037246108055115,
-0.11588885635137558,
0.05828530713915825,
0.03... | 0.112794 |
# Hermetic Execution Mode A Hermetic Build is a release engineering best practice for increasing the reliability and consistency of software builds. They are self-contained, and do not depend on anything outside of the build environment. This means they do not have network access, and cannot fetch dependencies at runti... | https://github.com/tektoncd/pipeline/blob/main/docs/hermetic.md | main | tekton | [
0.04720552638173103,
0.012629902921617031,
-0.06248322129249573,
-0.0005493595381267369,
-0.02036629244685173,
-0.047562114894390106,
-0.05671152472496033,
0.06356815993785858,
-0.095679372549057,
0.029880667105317116,
-0.004580206703394651,
-0.03875938430428505,
-0.07655930519104004,
-0.0... | 0.064507 |
# Tekton Controllers flags The different controllers `tektoncd/pipeline` ships come with a set of flags that can be changed (in the `yaml` payloads) for advanced use cases. This page documents them. ## Flag availability overview Not all flags are available on every controller. The table below shows which flags and envi... | https://github.com/tektoncd/pipeline/blob/main/docs/tekton-controller-flags.md | main | tekton | [
-0.0016646755393594503,
0.0036726039834320545,
-0.07507200539112091,
-0.03127939626574516,
-0.0005258837481960654,
-0.036696866154670715,
0.010832924395799637,
-0.013941856101155281,
0.03628956899046898,
0.04861951619386673,
0.03187114745378494,
-0.07986242324113846,
-0.029711220413446426,
... | 0.138496 |
only in the > variable name. ## `controller` The main controller binary ([`cmd/controller/main.go`](https://github.com/tektoncd/pipeline/blob/main/cmd/controller/main.go)) has additional flags to configure its behavior. ``` -disable-ha Whether to disable high-availability functionality for this component. This flag wil... | https://github.com/tektoncd/pipeline/blob/main/docs/tekton-controller-flags.md | main | tekton | [
0.021332217380404472,
0.0462794154882431,
-0.10517321527004242,
0.05378243327140808,
0.03175640478730202,
0.06272941827774048,
0.014665968716144562,
0.05837154760956764,
-0.06056154891848564,
-0.0026848046109080315,
0.0534907802939415,
0.0075365393422544,
0.014611482620239258,
0.0248261597... | 0.06745 |
# Cluster Resolver ## Resolver Type This Resolver responds to type `cluster`. ## Parameters | Param Name | Description | Example Value | |-------------|-------------------------------------------------------|----------------------------------| | `kind` | The kind of resource to fetch. | `task`, `pipeline`, `stepaction`... | https://github.com/tektoncd/pipeline/blob/main/docs/cluster-resolver.md | main | tekton | [
-0.07212124764919281,
-0.010287879034876823,
-0.041664570569992065,
0.04023747518658638,
-0.06080431863665581,
-0.06581882387399673,
-0.017689336091279984,
0.03715452551841736,
-0.02459695190191269,
0.013147617690265179,
-0.052428826689720154,
-0.03099741041660309,
0.00268412078730762,
-0.... | 0.138046 |
`default,other-namespace`, `\*`, (empty) | ## Usage ### Task Resolution ```yaml apiVersion: tekton.dev/v1beta1 kind: TaskRun metadata: name: remote-task-reference spec: taskRef: resolver: cluster params: - name: kind value: task - name: name value: some-task - name: namespace value: namespace-containing-task ``` ### Ta... | https://github.com/tektoncd/pipeline/blob/main/docs/cluster-resolver.md | main | tekton | [
-0.013247186318039894,
-0.03753359615802765,
-0.0377192348241806,
0.0010189214954152703,
0.015749743208289146,
-0.06346873939037323,
-0.028184929862618446,
-0.01588183268904686,
0.06236587464809418,
0.08341260999441147,
0.007871006615459919,
-0.04488450288772583,
-0.021558666601777077,
0.0... | 0.105947 |
# Affinity Assistants Affinity Assistant is a feature to coschedule `PipelineRun` `pods` to the same node based on [kubernetes pod affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity) so that it possible for the taskruns to execute parallel while shari... | https://github.com/tektoncd/pipeline/blob/main/docs/affinityassistants.md | main | tekton | [
0.002653861418366432,
-0.025952985510230064,
-0.02501801960170269,
0.025794170796871185,
-0.02916915901005268,
-0.02006644383072853,
-0.02627006731927395,
-0.06832700222730637,
0.0012726201675832272,
-0.023181241005659103,
-0.012797056697309017,
-0.058791108429431915,
-0.05241159722208977,
... | 0.175083 |
like OpenShift with Security Context Constraints (SCC). ### Default Behavior When you specify a ServiceAccount in your PipelineRun, the Affinity Assistant automatically inherits it: ```yaml apiVersion: tekton.dev/v1 kind: PipelineRun metadata: name: example-pipelinerun spec: taskRunTemplate: serviceAccountName: my-serv... | https://github.com/tektoncd/pipeline/blob/main/docs/affinityassistants.md | main | tekton | [
0.044156067073345184,
-0.04390352591872215,
-0.016162151470780373,
0.025507302954792976,
-0.019749760627746582,
-0.008380621671676636,
-0.005766918882727623,
-0.004532609600573778,
0.0156527291983366,
0.000293257791781798,
-0.00891757570207119,
-0.0738368034362793,
-0.014424788765609264,
0... | 0.14336 |
# Authentication at Run Time This document describes how Tekton handles authentication when executing `TaskRuns` and `PipelineRuns`. Since authentication concepts and processes apply to both of those entities in the same manner, this document collectively refers to `TaskRuns` and `PipelineRuns` as `Runs` for the sake o... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.05501013994216919,
0.04007910192012787,
-0.019028345122933388,
-0.03049217350780964,
-0.0040316591039299965,
-0.043573956936597824,
0.019186416640877724,
0.04554997384548187,
0.0826488584280014,
0.03532111644744873,
0.01612473838031292,
-0.02976878359913826,
-0.0054612914100289345,
0.01... | 0.208512 |
URL of the host for which you want Tekton to use that credential. In the following example, Tekton uses a `basic-auth` (username/password pair) `Secret` to access Git repositories at `github.com` and `gitlab.com` as well as Docker repositories at `gcr.io`: ```yaml apiVersion: v1 kind: Secret metadata: annotations: tekt... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.04907113313674927,
0.051042381674051285,
-0.06115114316344261,
-0.05640256777405739,
-0.04891732335090637,
-0.07383732497692108,
0.004363007843494415,
0.015651769936084747,
0.10651466995477676,
0.05622231215238571,
-0.036610767245292664,
-0.1246081069111824,
0.03922787308692932,
0.03584... | 0.005817 |
[Understanding credential selection](#understanding-credential-selection). 1. In `serviceaccount.yaml`, associate the `Secret` with the desired `ServiceAccount`: ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: build-bot secrets: - name: basic-user-pass ``` 1. In `run.yaml`, associate the `ServiceAccount` wi... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.06967399269342422,
-0.070075124502182,
-0.039795517921447754,
-0.03770700469613075,
-0.0631907656788826,
-0.032183438539505005,
0.0027823413256555796,
0.021254591643810272,
0.06593333929777145,
0.0423370860517025,
-0.019266754388809204,
-0.0936509519815445,
0.05346621200442314,
0.019489... | 0.034477 |
previous step. 1. In `serviceaccount.yaml`, associate the `Secret` with the desired `ServiceAccount`: ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: build-bot secrets: - name: ssh-key ``` 1. In `run.yaml`, associate the `ServiceAccount` with your `Run` by doing one of the following: - Associate the `Servic... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.014222360216081142,
-0.0509265772998333,
-0.05535665526986122,
-0.0317038893699646,
-0.06399185210466385,
-0.01472629513591528,
-0.03714112564921379,
0.026051653549075127,
0.045598335564136505,
0.059467025101184845,
0.01622120477259159,
-0.10057643800973892,
0.021856484934687614,
0.0377... | 0.025183 |
host-wide SSH key as a fallback \*\*Note:\*\* The order of secrets in the ServiceAccount does not affect credential matching. Tekton automatically orders SSH config entries so that host-wide credentials appear first (as fallbacks) and repo-specific credentials appear after. For a complete example, see [`git-ssh-auth-mu... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.06463165581226349,
-0.006001603789627552,
-0.07802537083625793,
-0.0491354763507843,
-0.0863865315914154,
-0.005826618988066912,
0.0600571371614933,
0.029452422633767128,
0.039184778928756714,
0.06004549562931061,
0.008470376022160053,
-0.036057692021131516,
0.08810275793075562,
0.07350... | 0.081522 |
desired `ServiceAccount`: ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: build-bot secrets: - name: regcred ``` 1. In `run.yaml`, associate the `ServiceAccount` with your `Run` by doing one of the following: - Associate the `ServiceAccount` with your `TaskRun`: ```yaml apiVersion: tekton.dev/v1beta1 kind: ... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.003362160176038742,
-0.040590446442365646,
-0.03631171956658363,
-0.037684980779886246,
-0.08757713437080383,
0.007406620308756828,
-0.02011187933385372,
0.03619765117764473,
0.06494759023189545,
0.05250106379389763,
0.007785140536725521,
-0.12392733246088028,
0.01932765729725361,
0.018... | 0.080726 |
ensure proper fallback behavior. The order of secrets in the ServiceAccount does not affect this. ### `basic-auth` for Docker Given URLs, usernames, and passwords of the form: `https://url{n}.com`, `user{n}`, and `pass{n}`, Tekton generates the following. Since Docker doesn't support the `kubernetes.io/ssh-auth` type `... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.031317900866270065,
0.10772284120321274,
0.006683721672743559,
-0.016167785972356796,
-0.013322905637323856,
-0.036020003259181976,
-0.0010896261082962155,
-0.03369227424263954,
0.09770255535840988,
0.005435810424387455,
-0.038701437413692474,
-0.10652252286672592,
0.02532794512808323,
... | -0.016425 |
by an `image-digest-exporter` Step you can safely ignore this message. The reason it appears is that this Step is injected by Tekton and it runs with a non-root UID that can differ from those of the Steps in the Task. The Step does not use these credentials. --- ## Disabling Tekton's Built-In Auth ### Why would an orga... | https://github.com/tektoncd/pipeline/blob/main/docs/auth.md | main | tekton | [
-0.0736490935087204,
0.060317378491163254,
-0.04658269137144089,
-0.028118658810853958,
0.030741166323423386,
-0.05856204032897949,
-0.007017028052359819,
-0.0018724629189819098,
0.04046432673931122,
0.015722693875432014,
-0.035174835473299026,
-0.06252755224704742,
0.05229634419083595,
0.... | 0.022192 |
# Matrix - [Overview](#overview) - [Configuring a Matrix](#configuring-a-matrix) - [Generating Combinations](#generating-combinations) - [Explicit Combinations](#explicit-combinations) - [Concurrency Control](#concurrency-control) - [Parameters](#parameters) - [Parameters in Matrix.Params](#parameters-in-matrixparams-1... | https://github.com/tektoncd/pipeline/blob/main/docs/matrix.md | main | tekton | [
-0.025484833866357803,
0.02061433158814907,
-0.14389286935329437,
0.04795698821544647,
-0.08653068542480469,
0.01610654592514038,
-0.02035563439130783,
-0.048892199993133545,
-0.044167209416627884,
0.004452587105333805,
0.020791077986359596,
-0.037262409925460815,
0.04598737880587578,
-0.0... | 0.013258 |
unique name of each `matrix` instance such that it is easier to distinguish all the instances based on their inputs. ```yaml pipelineSpec: tasks: - name: platforms-and-browsers displayName: "Platforms and Browsers: $(params.platform) and $(params.browser)" matrix: params: - name: platform value: - linux - mac - windows... | https://github.com/tektoncd/pipeline/blob/main/docs/matrix.md | main | tekton | [
-0.03071853518486023,
0.007564594969153404,
-0.0879359245300293,
-0.01677393727004528,
-0.04196159914135933,
-0.03982357680797577,
-0.010490461252629757,
-0.007332558743655682,
0.07897136360406876,
-0.056770555675029755,
-0.0027764090336859226,
-0.06707027554512024,
0.0007812061812728643,
... | 0.01521 |
Parameters in Matrix.Include.Params `Matrix.Include.Params` takes string replacements from `Parameters` of type String, Array or Object. ```yaml tasks: ... - name: task-4 taskRef: name: task-4 matrix: include: - name: foo-bar-rad params: - name: foo value: $(params.foo) # string replacement from string param - name: ba... | https://github.com/tektoncd/pipeline/blob/main/docs/matrix.md | main | tekton | [
-0.029034774750471115,
-0.0013582364190369844,
-0.08174704015254974,
0.031433094292879105,
-0.037519920617341995,
-0.05730815231800079,
-0.010752755217254162,
-0.028179679065942764,
0.026327969506382942,
-0.007844571024179459,
0.005141114350408316,
0.006225268356502056,
0.012747065164148808,... | 0.028098 |
during reconciliation, in which the whole `array` of `Results` can be consumed by another `pipelineTask` using the star notion [\*]. Note: A known limitation is not being able to consume a singular result or specific combinations of results produced by a previous fanned out `PipelineTask`. | Result Type in `taskRef` or... | https://github.com/tektoncd/pipeline/blob/main/docs/matrix.md | main | tekton | [
-0.042240217328071594,
0.03210131824016571,
-0.06414234638214111,
0.02625790610909462,
-0.08389970660209656,
-0.010228920727968216,
0.01527357567101717,
-0.035882942378520966,
0.004632089752703905,
-0.03291113302111626,
-0.07678377628326416,
-0.032309968024492264,
0.014485986903309822,
-0.... | 0.060455 |
to the original `matrix` combinations that include `"GOARCH": "linux/s390x"`: ```json! { "GOARCH": "linux/s390x", "version": "go1.17", "package": "path/to/common/package/", \*\*"flags": "-cover -v"\*\* } { "GOARCH": "linux/s390x", "version": "go1.18.1", "package": "path/to/common/package/", \*\*"flags": "-cover -v"\*\*... | https://github.com/tektoncd/pipeline/blob/main/docs/matrix.md | main | tekton | [
-0.04533553868532181,
0.011274851858615875,
-0.09584368765354156,
-0.04363028705120087,
0.038315966725349426,
0.016384931281208992,
0.01620173640549183,
-0.04874305799603462,
-0.024278759956359863,
-0.006837695837020874,
0.10297054797410965,
-0.01639016717672348,
-0.00043183285742998123,
0... | 0.054539 |
platform-browsers startTime: "2022-06-23T23:01:11Z" completionTime: "2022-06-23T23:01:20Z" conditions: - lastTransitionTime: "2022-06-23T23:01:20Z" message: 'Tasks Completed: 1 (Failed: 0, Cancelled 0), Skipped: 0' reason: Succeeded status: "True" type: Succeeded childReferences: - apiVersion: tekton.dev/v1beta1 kind: ... | https://github.com/tektoncd/pipeline/blob/main/docs/matrix.md | main | tekton | [
-0.028313186019659042,
0.02690509706735611,
-0.07194232940673828,
-0.025570763275027275,
0.059736739844083786,
-0.06544546037912369,
-0.04729052260518074,
-0.011875873431563377,
0.00586897786706686,
0.0052086664363741875,
-0.003724695648998022,
-0.08448244631290436,
-0.025506649166345596,
... | 0.028327 |
# Labels and Annotations Tekton allows you to use custom [Kubernetes Labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) to easily mark Tekton entities belonging to the same conceptual execution chain. Tekton also automatically adds select labels to more easily identify resource relations... | https://github.com/tektoncd/pipeline/blob/main/docs/labels.md | main | tekton | [
-0.007743550930172205,
0.03065839223563671,
-0.048317957669496536,
-0.015309398993849754,
-0.013406827114522457,
0.01532074250280857,
0.06097318232059479,
-0.0015340681420639157,
0.08338739722967148,
-0.030101049691438675,
-0.011456823907792568,
-0.13913126289844513,
-0.023079730570316315,
... | 0.200912 |
The same as above applies. | https://github.com/tektoncd/pipeline/blob/main/docs/labels.md | main | tekton | [
-0.025573987513780594,
0.0067045544274151325,
-0.00006630702409893274,
-0.015810701996088028,
0.04912123829126358,
0.000798138149548322,
-0.002593066543340683,
-0.011452725157141685,
0.0347382090985775,
-0.016067704185843468,
0.1081908568739891,
0.009331966750323772,
0.06735333055257797,
-... | 0.087498 |
# Resolver Reference Writing a resolver is made easier with the `github.com/tektoncd/pipeline/pkg/resolution/resolver/framework` package. This package exposes a number of interfaces that let your code control what kind of behaviour it should have when running. To get started really quickly see the [resolver template](.... | https://github.com/tektoncd/pipeline/blob/main/docs/resolver-reference.md | main | tekton | [
-0.06551357358694077,
0.013223990797996521,
-0.03013996221125126,
-0.005728984251618385,
-0.06986487656831741,
-0.061937879770994186,
-0.041269056499004364,
0.12342119961977005,
-0.019740162417292595,
0.033355046063661575,
-0.053921326994895935,
0.0062637608498334885,
-0.005162647459656,
0... | -0.017165 |
zombie requests remaining in an incomplete state forever. | Method to Implement | Description | |---------------------|-------------| | GetResolutionTimeout | Return a custom timeout duration from this method to control how long a resolution request to this resolver may take. | | https://github.com/tektoncd/pipeline/blob/main/docs/resolver-reference.md | main | tekton | [
-0.07432902604341507,
0.08331712335348129,
-0.019329508766531944,
-0.009425332769751549,
-0.058528099209070206,
-0.06621699780225754,
-0.08880025148391724,
0.011759706772863865,
-0.006680104415863752,
0.06272637844085693,
-0.02509237825870514,
0.007238138932734728,
-0.006883326917886734,
-... | 0.072128 |
# Pipeline Controller Metrics The following pipeline metrics are available at `controller-service` on port `9090`. Metrics are exported using [OpenTelemetry](https://opentelemetry.io/) and can be configured via the [observability ConfigMap](../config/config-observability.yaml). By default, Prometheus export is enabled.... | https://github.com/tektoncd/pipeline/blob/main/docs/metrics.md | main | tekton | [
-0.04782022535800934,
-0.012565471231937408,
-0.10541905462741852,
0.03611316159367561,
-0.06378693133592606,
-0.07996929436922073,
-0.028388384729623795,
0.05998780578374863,
0.0032278988510370255,
-0.02040821686387062,
-0.03651232272386551,
-0.1636226773262024,
-0.03344219550490379,
-0.0... | 0.137049 |
and pipelinerun metrics have these values: ``` yaml metrics.taskrun.level: "task" metrics.taskrun.duration-type: "histogram" metrics.pipelinerun.level: "pipeline" metrics.running-pipelinerun.level: "" metrics.pipelinerun.duration-type: "histogram" metrics.count.enable-reason: "false" ``` Following values are available ... | https://github.com/tektoncd/pipeline/blob/main/docs/metrics.md | main | tekton | [
0.02208688110113144,
-0.05749061331152916,
-0.04637245461344719,
0.02143995463848114,
-0.049863480031490326,
0.030845537781715393,
0.005954788997769356,
0.03085276111960411,
-0.022066863253712654,
-0.08034896850585938,
-0.04717632383108139,
-0.1274319738149643,
-0.0008440912351943552,
0.01... | 0.057342 |
# Metrics Migration: OpenCensus to OpenTelemetry \*\*Breaking Changes - Action Required\*\* Related PR: [#9043](https://github.com/tektoncd/pipeline/pull/9043) --- ## Executive Summary Tekton Pipelines has migrated from \*\*OpenCensus\*\* (deprecated) to \*\*OpenTelemetry\*\* (CNCF standard). This is a \*\*BREAKING CHA... | https://github.com/tektoncd/pipeline/blob/main/docs/metrics-migration-otel.md | main | tekton | [
-0.04399923235177994,
0.02891431376338005,
-0.03732936829328537,
-0.04057306796312332,
0.025250673294067383,
-0.09753493964672089,
-0.04369279742240906,
0.001996326260268688,
0.0023332664277404547,
0.02687430940568447,
0.006654525175690651,
-0.05773714557290077,
-0.02294081449508667,
-0.02... | 0.084724 |
`CancelledRunFinally` \*\*⚠️ Cardinality Impact:\*\* Enabling this increases time series by 3-5x. Use `sum by(le)` aggregation in queries to mitigate. \*\*Note:\*\* Total counters (`\*\_total`) never include the `reason` label, even when enabled. ### 2.3 Preserved Behavior | Feature | Implementation | | :---- | :---- |... | https://github.com/tektoncd/pipeline/blob/main/docs/metrics-migration-otel.md | main | tekton | [
-0.004294999409466982,
-0.019503489136695862,
0.010729113593697548,
0.03044699877500534,
-0.022200338542461395,
0.012668232433497906,
0.05487076938152313,
-0.0016614003106951714,
0.03063308447599411,
-0.0063654095865786076,
-0.00976645853370428,
-0.10554111003875732,
0.00042042607674375176,
... | 0.14063 |
:---- | :---- | | `rate(tekton\_pipelines\_controller\_workqueue\_adds\_total[5m])` | `rate(kn\_workqueue\_adds\_total[5m])` | | `tekton\_pipelines\_controller\_pipelinerun\_duration\_seconds` | ✅ \*\*No change needed\*\* | | `tekton\_pipelines\_controller\_go\_goroutines` | `go\_goroutines` | \*\*Note:\*\* Core Tekton... | https://github.com/tektoncd/pipeline/blob/main/docs/metrics-migration-otel.md | main | tekton | [
-0.016230344772338867,
0.003868061350658536,
-0.07826939970254898,
0.015935415402054787,
-0.06504561007022858,
-0.0833122506737709,
-0.005793269723653793,
0.002784201642498374,
0.035229574888944626,
0.029276955872774124,
0.049601126462221146,
-0.10442163050174713,
-0.031935930252075195,
-0... | 0.074831 |
Can I use both OpenCensus and OpenTelemetry?\*\* A: No. The controller only emits OpenTelemetry metrics after upgrade. \*\*Q: How do I test without affecting production?\*\* A: Deploy in a test/staging environment first. Verify all metrics, dashboards, and alerts work before upgrading production. \*\*Q: Where can I get... | https://github.com/tektoncd/pipeline/blob/main/docs/metrics-migration-otel.md | main | tekton | [
-0.011889110319316387,
-0.0209292471408844,
-0.07000980526208878,
0.017916491255164146,
-0.043363142758607864,
-0.09514865279197693,
-0.058287885040044785,
-0.011083810590207577,
-0.04753554239869118,
0.05877123400568962,
0.07397592067718506,
-0.0858849585056305,
-0.01856335997581482,
-0.0... | 0.066803 |
# HTTP Resolver This resolver responds to type `http`. ## Parameters | Param Name | Description | Example Value | | | -------------------------- | -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------... | https://github.com/tektoncd/pipeline/blob/main/docs/http-resolver.md | main | tekton | [
-0.06057635322213173,
0.05158521234989166,
0.023582331836223602,
0.0068835061974823475,
-0.13012154400348663,
-0.07038689404726028,
-0.052115149796009064,
0.03992098569869995,
0.005046837497502565,
-0.017178446054458618,
-0.04033268988132477,
-0.06290440261363983,
0.021866651251912117,
-0.... | 0.02762 |
⚠️ This is a work in progress: SPIRE support is not yet functional TaskRun result attestations is currently an alpha experimental feature. Currently all that is implemented is support for configuring Tekton to connect to SPIRE. See TEP-0089 for details on the overall design and feature set. This being a large feature, ... | https://github.com/tektoncd/pipeline/blob/main/docs/spire.md | main | tekton | [
-0.07234732806682587,
0.027023782953619957,
-0.026884837076067924,
0.04244527965784073,
0.0136263994500041,
-0.024307100102305412,
-0.01614558696746826,
0.009091729298233986,
-0.07682078331708908,
0.06286008656024933,
-0.08641763776540756,
-0.05341678857803345,
0.0055261109955608845,
0.073... | 0.031574 |
be used. 1. Register the SPIRE workload entry for Tekton with the "Admin" flag, which will allow the Tekton controller to communicate with the SPIRE server to manage the TaskRun identities dynamically. ``` # This example is assuming use of the above SPIRE deployment # Example where trust domain is "example.org" and clu... | https://github.com/tektoncd/pipeline/blob/main/docs/spire.md | main | tekton | [
-0.020618759095668793,
0.006691077258437872,
-0.08531377464532852,
0.022769110277295113,
-0.06363659352064133,
-0.005860086530447006,
0.023492468520998955,
0.023014908656477928,
0.031734827905893326,
0.07035714387893677,
-0.05089274048805237,
-0.11195917427539825,
0.009085520170629025,
-0.... | 0.10712 |
# StepActions - [Overview](#overview) - [Configuring a StepAction](#configuring-a-stepaction) - [Declaring Parameters](#declaring-parameters) - [Passing Params to StepAction](#passing-params-to-stepaction) - [Emitting Results](#emitting-results) - [Fetching Emitted Results from StepActions](#fetching-emitted-results-fr... | https://github.com/tektoncd/pipeline/blob/main/docs/stepactions.md | main | tekton | [
-0.06986947357654572,
0.00007163229747675359,
-0.06351723521947861,
0.027558915317058563,
0.0019699425902217627,
0.031045343726873398,
0.05428773909807205,
0.036946460604667664,
-0.03613753989338875,
0.005770307499915361,
0.04111161455512047,
-0.033893126994371414,
0.08274272084236145,
-0.... | 0.078627 |
it with `params`, just like how a `TaskRun` provides params to the underlying `Task`. ```yaml apiVersion: tekton.dev/v1 kind: Task metadata: name: step-action spec: params: - name: param-for-step-action description: "this is a param that the step action needs." steps: - name: action-runner ref: name: step-action params... | https://github.com/tektoncd/pipeline/blob/main/docs/stepactions.md | main | tekton | [
-0.11752732843160629,
0.013446299359202385,
-0.02665392868220806,
0.024685751646757126,
0.003042003372684121,
0.005594360642135143,
-0.02325095422565937,
0.001893284497782588,
0.025729410350322723,
0.011699464172124863,
-0.01485730055719614,
-0.031130652874708176,
0.007838686928153038,
0.0... | 0.097784 |
- name: digest description: "digest of the image" value: $(steps.kaniko.results.digest) steps: - name: git-clone ref: name: clone-step-action - name: kaniko ref: name: kaniko-step-action ``` #### Passing Results between Steps `StepResults` (i.e. results written to `$(step.results..path)`, NOT `$(results..path)`) can be... | https://github.com/tektoncd/pipeline/blob/main/docs/stepactions.md | main | tekton | [
0.015070358291268349,
0.05355724319815636,
0.01919238083064556,
0.05130196735262871,
-0.004929660353809595,
-0.017010951414704323,
-0.01183084212243557,
0.0440664179623127,
0.06429190933704376,
-0.04016325995326042,
0.00033190587419085205,
-0.02696242928504944,
-0.01922374591231346,
-0.007... | 0.044322 |
kind: StepAction metadata: name: myStep spec: description: my step params: ... volumeMounts: ... image: ... script: ... ``` ### Referencing a StepAction `StepActions` can be referenced from the `Step` using the `ref` field, as follows: ```yaml apiVersion: tekton.dev/v1 kind: TaskRun metadata: name: step-action-run spec... | https://github.com/tektoncd/pipeline/blob/main/docs/stepactions.md | main | tekton | [
-0.05329617112874985,
-0.01019530650228262,
-0.01026933267712593,
0.002513458486646414,
0.02294878475368023,
0.009673943743109703,
-0.020308805629611015,
0.04763690009713173,
0.04230634123086929,
0.0221407450735569,
-0.0118250148370862,
-0.050264373421669006,
-0.005740400869399309,
0.01280... | 0.061813 |
# How to write a Resolver This how-to will outline the steps a developer needs to take when creating a new (very basic) Resolver. Rather than focus on support for a particular version control system or cloud platform this Resolver will simply respond with some hard-coded YAML. If you aren't yet familiar with the meanin... | https://github.com/tektoncd/pipeline/blob/main/docs/how-to-write-a-resolver.md | main | tekton | [
-0.08285665512084961,
0.014627284370362759,
0.045892298221588135,
-0.03538982570171356,
-0.06656445562839508,
-0.07073195278644562,
-0.0817052572965622,
0.04577632248401642,
0.06164557859301567,
0.0697239562869072,
-0.08690883964300156,
-0.035610489547252655,
-0.00879049301147461,
-0.04829... | 0.127902 |
"knative.dev/pkg/injection/sharedmain" ) func main() { sharedmain.Main("controller", framework.NewController(context.Background(), &resolver{}), ) } type resolver struct {} ``` {{% /tab %}} {{% /tabs %}} This won't compile yet but you can download the dependencies by running: ```bash # Depending on your go version you ... | https://github.com/tektoncd/pipeline/blob/main/docs/how-to-write-a-resolver.md | main | tekton | [
-0.0244522076100111,
-0.0037868984509259462,
-0.04980039224028587,
-0.04682372882962227,
-0.04684344306588173,
-0.012493642047047615,
-0.00047319201985374093,
0.08179520815610886,
-0.06445779651403427,
0.03638139367103577,
0.04403159022331238,
-0.05772855877876282,
-0.04386552795767784,
0.... | -0.003085 |
return err } if u.Scheme != "demoscheme" { return fmt.Errorf("Invalid Scheme. Want %s, Got %s", "demoscheme", u.Scheme) } if u.Path == "" { return errors.New("Empty path.") } return nil } ``` You'll also need to add the `net/url` as `neturl` and `"errors"` package to your list of imports at the top of the file. ``` {{%... | https://github.com/tektoncd/pipeline/blob/main/docs/how-to-write-a-resolver.md | main | tekton | [
-0.0046675242483615875,
0.0035525436978787184,
-0.090790294110775,
-0.018129723146557808,
-0.03484465554356575,
-0.04917525127530098,
0.05871421471238136,
0.12755687534809113,
-0.09906596690416336,
-0.008546420373022556,
-0.05578944459557533,
-0.08653932064771652,
0.00683470256626606,
0.09... | 0.029343 |
to resolve the requested file or resource. func (r \*resolver) Resolve(ctx context.Context, req \*v1beta1.ResolutionRequestSpec) (framework.ResolvedResource, error) { return &myResolvedResource{}, nil } // our hard-coded resolved file to return const pipeline = ` apiVersion: tekton.dev/v1beta1 kind: Pipeline metadata: ... | https://github.com/tektoncd/pipeline/blob/main/docs/how-to-write-a-resolver.md | main | tekton | [
-0.09401368349790573,
0.058261532336473465,
0.003383415751159191,
0.022077400237321854,
-0.036928799003362656,
-0.06836098432540894,
0.00534867262467742,
0.07438091933727264,
-0.03136816248297691,
0.001394264167174697,
-0.10225461423397064,
-0.07384304702281952,
-0.06803660094738007,
0.052... | 0.065343 |
let's submit a request for its hard-coded pipeline. Create a file called `test-request.yaml` with the following content: ```yaml apiVersion: resolution.tekton.dev/v1beta1 kind: ResolutionRequest metadata: name: test-request labels: resolution.tekton.dev/type: demo ``` And submit this request with the following command:... | https://github.com/tektoncd/pipeline/blob/main/docs/how-to-write-a-resolver.md | main | tekton | [
0.030507799237966537,
-0.0028248364105820656,
-0.023667525500059128,
-0.03216571360826492,
-0.04415177181363106,
-0.08022820204496384,
-0.06995990127325058,
0.024011824280023575,
0.07266751676797867,
0.07979044318199158,
-0.04646196961402893,
-0.09357839822769165,
-0.047084417194128036,
-0... | 0.08524 |
# Migrating from v1alpha1.Run to v1beta1.CustomRun This document describes how to migrate from `v1alpha1.Run` and `v1beta1.CustomRun` - [Changes to fields](#changes-to-fields) - [Changes to the specification](#changes-to-the-specification) - [Changes to the reference](#changes-to-the-reference) - [Support `PodTemplate`... | https://github.com/tektoncd/pipeline/blob/main/docs/migrating-v1alpha1.Run-to-v1beta1.CustomRun.md | main | tekton | [
0.022341620177030563,
-0.009705450385808945,
0.007476653438061476,
-0.02392195537686348,
0.04156586900353432,
0.014636601321399212,
-0.08092345297336578,
0.017532410100102425,
-0.05376708507537842,
0.02008165419101715,
-0.018409382551908493,
-0.005529511254280806,
-0.09046480059623718,
-0.... | 0.0835 |
Succeeded Status: Unknown Reason: Running ``` Now it failed for some reasons but has remaining retries, instead of setting Conditions as failed on TimedOut: ```yaml Status: Conditions: - Type: Succeeded Status: False Reason: Failed ``` We \*\*recommend\*\* you to do archive the failure status to `customRun.Status.retri... | https://github.com/tektoncd/pipeline/blob/main/docs/migrating-v1alpha1.Run-to-v1beta1.CustomRun.md | main | tekton | [
0.002544447546824813,
-0.04673530161380768,
-0.013813436031341553,
-0.007219589315354824,
0.013881610706448555,
-0.01052936166524887,
-0.05268425866961479,
-0.0008847306598909199,
-0.08448051661252975,
0.008016061969101429,
-0.02113652229309082,
-0.038033436983823776,
-0.0321207232773304,
... | 0.032239 |
# TaskRuns - [Overview](#overview) - [Configuring a `TaskRun`](#configuring-a-taskrun) - [Specifying the target `Task`](#specifying-the-target-task) - [Tekton Bundles](#tekton-bundles) - [Remote Tasks](#remote-tasks) - [Specifying `Parameters`](#specifying-parameters) - [Propagated Parameters](#propagated-parameters) -... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.039213601499795914,
0.027087651193141937,
-0.0342029444873333,
0.022113962098956108,
0.013560584746301174,
-0.002244020579382777,
0.01844276487827301,
0.020770953968167305,
-0.07024145871400833,
0.037665482610464096,
0.012216426432132721,
-0.12022880464792252,
-0.0011998825939372182,
0.... | 0.140739 |
and requires enabling [beta features](./additional-configs.md#beta-features). ```yaml spec: taskRef: resolver: bundles params: - name: bundle value: docker.io/myrepo/mycatalog - name: name value: echo-task - name: kind value: Task ``` You may also specify a `tag` as you would with a Docker image which will give you a r... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.030677594244480133,
-0.0035684083122760057,
0.004085236229002476,
0.0206895861774683,
0.028736334294080734,
-0.005887736100703478,
0.0644218921661377,
0.0017348480178043246,
-0.027310313656926155,
0.004647493362426758,
-0.05691537261009216,
-0.04911008104681969,
-0.0024984092451632023,
... | 0.072013 |
# or tekton.dev/v1beta1 kind: TaskRun metadata: generateName: object-param-result- spec: params: - name: gitrepo value: commit: sha123 url: xyz.com taskSpec: steps: - name: echo-object-params image: bash args: - echo - --url=$(params.gitrepo.url) - --commit=$(params.gitrepo.commit) ``` On executing the task run, the ob... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.023533301427960396,
0.008164117112755775,
-0.06002262979745865,
0.01243971660733223,
-0.02599002979695797,
-0.09063012897968292,
-0.05382943153381348,
0.029781747609376907,
0.041367802768945694,
0.07513898611068726,
0.0003622014191932976,
-0.024447603151202202,
-0.02356312796473503,
0.0... | 0.072428 |
one or more `Workspaces`, you must map those `Workspaces` to the corresponding physical volumes in your `TaskRun` definition. For example, you can map a `PersistentVolumeClaim` volume to a `Workspace` as follows: ```yaml workspaces: - name: myworkspace # must match workspace name in the Task persistentVolumeClaim: clai... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.03847535327076912,
-0.14344176650047302,
-0.021951979026198387,
0.0005202721804380417,
-0.015251469798386097,
0.0007711462094448507,
0.00043529117829166353,
0.036694031208753586,
0.018259305506944656,
0.001964787021279335,
-0.0024138945154845715,
-0.06109735742211342,
0.056144192814826965... | 0.009917 |
"Error" if a `Sidecar` exits with an error, disregarding the exit codes of the container images that actually executed the `Steps` inside the `Pod`. Only the above command is affected. The `Pod's` description correctly denotes a "Failed" status and the container statuses correctly denote their exit codes and reasons. #... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
0.0030065712053328753,
0.03024393692612648,
0.007657971233129501,
-0.008970648981630802,
0.05168084427714348,
-0.04010899364948273,
-0.03429286554455757,
0.030149217694997787,
-0.03456806764006615,
0.012753060087561607,
0.030986610800027847,
-0.056581154465675354,
-0.018584419041872025,
0.... | 0.09769 |
are `1h30m`, `1h`, `1m`, `60s`, and `0`. If a `TaskRun` runs longer than its timeout value, the pod associated with the `TaskRun` will be deleted. This means that the logs of the `TaskRun` are not preserved. The deletion of the `TaskRun` pod is necessary in order to stop `TaskRun` step containers from running. The glob... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
0.0383579321205616,
0.04186445474624634,
-0.02223077602684498,
-0.0006771966582164168,
0.026689890772104263,
-0.036447618156671524,
-0.08476980030536652,
-0.00523777399212122,
0.0657874345779419,
0.03969671204686165,
0.0008705378859303892,
-0.01546434685587883,
-0.047805991023778915,
0.029... | 0.088043 |
redundant. - [`sidecars`](tasks.md#using-a-sidecar-in-a-task) - This field is a list. The list has one entry per `sidecar` in the manifest. Each entry represents the imageid of the corresponding sidecar. - `spanContext` - Contains tracing span context fields. ## Monitoring execution status As your `TaskRun` executes, i... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
0.03700010105967522,
0.05149144306778908,
0.025939010083675385,
0.015432283282279968,
0.10928046703338623,
-0.020649656653404236,
0.029591679573059082,
0.023550089448690414,
-0.008843543007969856,
0.015312347561120987,
0.00834541767835617,
-0.03589634224772453,
0.022590860724449158,
0.0057... | 0.190065 |
False | TaskRunTimeout | n/a | Yes | The TaskRun timed out. | | False | TaskRunImagePullFailed | n/a | Yes | The TaskRun failed due to one of its steps not being able to pull the image. | | False | FailureIgnored | n/a | Yes | The TaskRun failed but the failure was ignored. | When a `TaskRun` changes status, [events](e... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.03790038451552391,
0.006798757705837488,
0.006492165382951498,
0.02175549976527691,
0.04383549466729164,
-0.035874105989933014,
0.008261107839643955,
-0.03292997553944588,
0.09610173106193542,
0.038456887006759644,
0.03187931701540947,
0.006876676343381405,
0.02868468128144741,
0.024390... | 0.156509 |
cancel a TaskRun, the running pod associated with that `TaskRun` is deleted. This means that the logs of the `TaskRun` are not preserved. The deletion of the `TaskRun` pod is necessary in order to stop `TaskRun` step containers from running. \*\*Note: if `keep-pod-on-cancel` is set to `"true"` in the `feature-flags`, t... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.010301552712917328,
0.03483184427022934,
0.022581560537219048,
0.021120211109519005,
0.07176968455314636,
-0.031319666653871536,
-0.008939415216445923,
-0.04739857465028763,
0.060745805501937866,
0.06692967563867569,
0.019864020869135857,
0.019698427990078926,
-0.03567642718553543,
0.01... | 0.127918 |
- --destination=gcr.io/my-project/gohelloworld ``` ### Example of Using custom `ServiceAccount` credentials The example below illustrates how to specify a `ServiceAccount` to access a private `git` repository: ```yaml apiVersion: tekton.dev/v1 # or tekton.dev/v1beta1 kind: TaskRun metadata: name: test-task-with-service... | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.04294425621628761,
-0.05758380517363548,
-0.09204356372356415,
-0.03344879671931267,
-0.06350226700305939,
-0.020888060331344604,
0.07181696593761444,
0.04117083549499512,
0.06718045473098755,
0.05864899232983589,
0.03521575406193733,
-0.09466495364904404,
0.05279356986284256,
0.0826766... | 0.053301 |
- Processing step results and artifacts --- Except as otherwise noted, the content of this page is licensed under the [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/), and code samples are licensed under the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0). | https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | main | tekton | [
-0.07913731783628464,
0.018648676574230194,
-0.05311848223209381,
-0.03573693335056305,
0.108153335750103,
-0.11866499483585358,
-0.08610805124044418,
-0.05590387061238289,
-0.012273889034986496,
0.03232651948928833,
0.0021997843869030476,
0.04709846153855324,
0.016184953972697258,
-0.0767... | 0.128464 |
# Events in Tekton Tekton's controllers emits [Kubernetes events](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#event-v1-core) when `TaskRuns` and `PipelineRuns` execute. This allows you to monitor and react to what's happening during execution by retrieving those events using the `kubectl descri... | https://github.com/tektoncd/pipeline/blob/main/docs/events.md | main | tekton | [
-0.03399219363927841,
0.032221805304288864,
0.014770525507628918,
0.003937744535505772,
0.04757169261574745,
-0.07004661113023758,
0.0024959621950984,
-0.04859571158885956,
0.164095938205719,
0.04914022237062454,
-0.022529104724526405,
-0.12171322852373123,
-0.036908622831106186,
-0.026728... | 0.158964 |
the core reconciler (no `Succeeded` condition set yet). It provides early notification that the resource exists and is waiting to be processed. CloudEvents are only sent when enabled in the [configuration](./additional-configs.md#configuring-cloudevents-notifications). ## Event formats The `tekton-events-controller` se... | https://github.com/tektoncd/pipeline/blob/main/docs/events.md | main | tekton | [
-0.0585688091814518,
-0.007964490912854671,
0.016901833936572075,
0.018244996666908264,
0.04659230262041092,
-0.05073774605989456,
-0.005928843282163143,
-0.06661315262317657,
0.13167908787727356,
0.030849751085042953,
-0.0037332368083298206,
-0.07586253434419632,
-0.044017042964696884,
0.... | 0.032009 |
# Variable Substitutions Supported by `Tasks` and `Pipelines` This page documents the variable substitutions supported by `Tasks` and `Pipelines`. For instructions on using variable substitutions see the relevant section of [the Tasks doc](tasks.md#using-variable-substitution). \*\*Note:\*\* Tekton does not escape the ... | https://github.com/tektoncd/pipeline/blob/main/docs/variables.md | main | tekton | [
-0.034989237785339355,
0.057059288024902344,
0.0038734888657927513,
0.02758386917412281,
-0.08285512030124664,
-0.00933139119297266,
0.0454244539141655,
0.018301041796803474,
-0.0468863807618618,
-0.002705658320337534,
-0.058637842535972595,
-0.07775242626667023,
0.0290855560451746,
0.0457... | 0.090168 |
the `Task` | ## Variables available in a `Task` | Variable | Description | |----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| | `params.` | The value of the parameter at runtime. | | `par... | https://github.com/tektoncd/pipeline/blob/main/docs/variables.md | main | tekton | [
-0.016346588730812073,
0.04220166057348251,
-0.12858887016773224,
0.02698219195008278,
-0.09444800764322281,
-0.0061242468655109406,
0.062192924320697784,
0.07706720381975174,
-0.050760794430971146,
-0.0016050549456849694,
0.015340560115873814,
-0.021181948482990265,
0.02771342545747757,
-... | 0.10196 |
| | `Task` | `spec.sidecars[].env.value` | | `Task` | `spec.sidecars[].env.valueFrom.secretKeyRef.name` | | `Task` | `spec.sidecars[].env.valueFrom.secretKeyRef.key` | | `Task` | `spec.sidecars[].env.valueFrom.configMapKeyRef.name` | | `Task` | `spec.sidecars[].env.valueFrom.configMapKeyRef.key` | | `Task` | `spec.side... | https://github.com/tektoncd/pipeline/blob/main/docs/variables.md | main | tekton | [
0.04151327535510063,
-0.03698240593075752,
-0.11204728484153748,
-0.004813597537577152,
0.017056822776794434,
-0.0022194022312760353,
0.059671882539987564,
0.08305216580629349,
-0.060383036732673645,
0.00845479965209961,
0.04014519229531288,
-0.060376785695552826,
0.08817358314990997,
-0.0... | -0.022063 |
This document describes additional options to configure your Tekton Pipelines installation. ## Table of Contents - [Configuring built-in remote Task and Pipeline resolution](#configuring-built-in-remote-task-and-pipeline-resolution) - [Configuring CloudEvents notifications](#configuring-cloudevents-notifications) - [Co... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
-0.012329024262726307,
0.018479811027646065,
-0.02888392098248005,
-0.03088143840432167,
-0.04227522388100624,
-0.01576714776456356,
-0.06791579723358154,
0.03884536400437355,
-0.05795624479651451,
0.034106332808732986,
-0.017981762066483498,
-0.07939957827329636,
-0.02774236537516117,
0.0... | 0.029885 |
a `PodTemplate`. The environment variables specified by a `PodTemplate` supercedes all other ways of specifying environment variables. However, there exists a configuration i.e. `default-forbidden-env`, the environment variable specified in this list cannot be updated via a `PodTemplate`. For example: ```yaml apiVersio... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
0.05933859199285507,
-0.010067006573081017,
-0.01162707805633545,
-0.04618936404585838,
0.008998037315905094,
-0.016282819211483,
-0.011491631157696247,
0.007785975933074951,
0.004300548695027828,
0.05561099201440811,
-0.00042514887172728777,
-0.08658401668071747,
-0.06634663045406342,
0.0... | 0.057055 |
(`ServiceAccount`), timeout (`Timeout`), resolver (`Resolver`), and Pod template (`PodTemplate`) values used by Tekton Pipelines in `TaskRun` and `PipelineRun` definitions. To do so, modify the ConfigMap `config-defaults` with your desired values. The example below customizes the following: - the default service accoun... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
0.027593867853283882,
0.04377030208706856,
0.004448110703378916,
0.03607184439897537,
-0.05180540680885315,
-0.008760669268667698,
-0.04408564791083336,
0.012511572800576687,
0.07987883687019348,
0.05793144553899765,
-0.04989028722047806,
-0.035907719284296036,
-0.014761772006750107,
-0.01... | 0.163371 |
lead to unexpected behaviour with Tasks that use sidecars, or in clusters that use injected sidecars (e.g. Istio). Setting this flag to `"false"` will mean the `running-in-environment-with-injected-sidecars` flag has no effect. - `running-in-environment-with-injected-sidecars`: set this flag to `"false"` to allow the T... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
0.02252618595957756,
-0.04876333102583885,
-0.05157506838440895,
0.08752355724573135,
0.04899193346500397,
-0.03423378989100456,
-0.06713170558214188,
0.004009384196251631,
0.03457847982645035,
0.04765841364860535,
0.012569593265652657,
-0.06608693301677704,
0.02159539796411991,
0.08140681... | 0.15781 |
to `"false"`. - `set-security-context`: Set this flag to `true` to set a security context for containers injected by Tekton that will allow TaskRun pods to run in namespaces with `restricted` pod security admission. By default, this is set to `false`. - `set-security-context-read-only-root-filesystem`: Set this flag to... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
0.054007016122341156,
0.045315250754356384,
-0.05727440118789673,
0.003568192943930626,
0.01959850825369358,
-0.0037127966061234474,
0.060359060764312744,
0.016676010563969612,
0.029967453330755234,
0.050476498901844025,
0.004844190552830696,
-0.05483477935194969,
-0.026789527386426926,
0.... | 0.171191 |
limit. To exceed this limit of 4096 bytes, you can enable larger results using sidecar logs. By enabling this feature, you will have a configurable limit (with a default of 4096 bytes) per result with no restriction on the number of results. The results are still stored in the taskRun CRD, so they should not exceed the... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
0.06556200236082077,
0.0449661947786808,
-0.0046900799497962,
-0.004191360902041197,
-0.017083140090107918,
-0.029345232993364334,
-0.0662308856844902,
0.04926932975649834,
0.008335953578352928,
0.06752326339483261,
-0.03247736394405365,
-0.06506119668483734,
-0.04454445838928223,
-0.01729... | 0.100416 |
to customize the container images built and used by Tekton Pipelines. ## Verify Tekton Pipelines Release > We will refine this process over time to be more streamlined. For now, please follow the steps listed in this section to verify Tekton pipeline release. Tekton Pipeline's images are being signed by [Tekton Chains]... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
-0.044680770486593246,
0.10547902435064316,
-0.022876223549246788,
-0.07487419247627258,
0.013930181972682476,
-0.10718003660440445,
-0.009751138277351856,
0.06094170734286308,
-0.027235334739089012,
-0.005427568685263395,
0.027187852188944817,
-0.06003115698695183,
0.009670739062130451,
0... | 0.035964 |
Verify Tekton Resources Trusted Resources is a feature to verify Tekton Tasks and Pipelines. The current version of feature supports `v1beta1` `Task` and `Pipeline`. For more details please take a look at [Trusted Resources](./trusted-resources.md). ## Pipelineruns with Affinity Assistant The cluster operators can revi... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
-0.05956541746854782,
-0.016304485499858856,
-0.06378041207790375,
0.039390165358781815,
0.05424351617693901,
-0.08845264464616776,
0.002441863063722849,
-0.0008715405710972846,
-0.034979596734046936,
0.0032982470002025366,
0.04575322940945625,
-0.03392192721366882,
-0.010590407997369766,
... | 0.108923 |
the backoff parameters (such as initial duration, factor, steps, and cap) using the `wait-exponential-backoff` ConfigMap: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: wait-exponential-backoff namespace: tekton-pipelines data: duration: "1s" factor: "2.0" jitter: "0.0" steps: "10" cap: "30s" ``` - \*\*duration... | https://github.com/tektoncd/pipeline/blob/main/docs/additional-configs.md | main | tekton | [
-0.07938452064990997,
-0.014219876378774643,
-0.08426836878061295,
0.035575833171606064,
-0.027002591639757156,
-0.026379399001598358,
-0.015320362523198128,
0.0068722921423614025,
-0.01372507680207491,
0.030290931463241577,
0.06006431579589844,
-0.05051339790225029,
0.00042988185305148363,
... | 0.145164 |
# Resolver Template This directory contains a working Resolver based on the instructions from the [developer howto in the docs](../how-to-write-a-resolver.md). ## Resolver Type This Resolver responds to type `demo`. ## Parameters | Name | Desccription | Example Value | |--------|------------------------------|---------... | https://github.com/tektoncd/pipeline/blob/main/docs/resolver-template/README.md | main | tekton | [
-0.11569975316524506,
-0.025027599185705185,
-0.015562497079372406,
-0.04463398829102516,
-0.0273800827562809,
-0.08366256207227707,
-0.08043204247951508,
0.07499323040246964,
-0.014974758960306644,
0.053784631192684174,
0.004081366118043661,
0.013385182246565819,
0.003277071285992861,
0.0... | -0.006755 |
# Results Lifecycle This section gives an overview of the results lifecycle in `Tekton Pipelines`. ## Results definition and usage Tasks can define results by adding a result on the Task spec. For more information, see ["Emitting Results"](../tasks.md#emitting-results). Users are encouraged to use variable substitution... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/results-lifecycle.md | main | tekton | [
-0.03490343689918518,
0.04810232296586037,
-0.07457201927900314,
0.05465395748615265,
0.01089161541312933,
-0.037145957350730896,
-0.04081335663795471,
0.06553729623556137,
0.040061723440885544,
0.01904628612101078,
0.0087183378636837,
-0.03435870632529259,
-0.012936213985085487,
0.0208293... | 0.112827 |
## Kubernetes objects Before learning about how Tekton works, it's useful to take some time to understand what a Kubernetes object is. Please see [Understanding Kubernetes objects](https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/) for an overview of working with objects. Kubernetes ... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/controller-logic.md | main | tekton | [
-0.07380719482898712,
0.01953066885471344,
-0.00736594945192337,
-0.03177661448717117,
-0.03526837378740311,
-0.026703432202339172,
0.03499683737754822,
0.036031290888786316,
0.08324059098958969,
0.028765728697180748,
-0.011943694204092026,
-0.06803406774997711,
-0.0363171212375164,
-0.025... | 0.246053 |
a pod to run the TaskRun and exits the reconcile loop. Later, the pod completes, resulting in another event that triggers reconciliation of the TaskRun that owns it. The reconciler sees that the TaskRun has a pod associated with it, and that the pod has completed. It updates the TaskRun status to mark it as completed a... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/controller-logic.md | main | tekton | [
0.0042096939869225025,
-0.015842100605368614,
0.05865811929106712,
0.021243184804916382,
0.07309150695800781,
-0.032061103731393814,
-0.013196823187172413,
-0.05396660417318344,
0.09525804966688156,
0.009508540853857994,
-0.01120503805577755,
0.05774463713169098,
-0.061801712960004807,
-0.... | 0.194867 |
# Support for running in multi-tenant configuration Multi-tenancy for Tekton is intended as running multiple instances of the Tekton control plane in a single Kubernetes cluster, with each control plane responsible for reconciliation of the Tekton resources in a single namespace. This type of setup involves various asp... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/multi-tenant-support.md | main | tekton | [
-0.05913015455007553,
0.034213837236166,
-0.06341128051280975,
-0.01496325246989727,
-0.02938816510140896,
-0.03545723855495453,
0.008569133467972279,
-0.014803513884544373,
0.0671810656785965,
0.030602186918258667,
0.013632353395223618,
-0.1340532898902893,
0.014872872270643711,
-0.053698... | 0.13633 |
in the cluster. The conversion webhook is bundled in a single binary with the other webhooks, so today it's not possible to run multiple validation and mutation webhooks and a single conversion webhook. [TEP-0129](https://github.com/tektoncd/community/blob/main/teps/0129-multiple-tekton-instances-per-cluster.md) will c... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/multi-tenant-support.md | main | tekton | [
-0.08585168421268463,
0.034005314111709595,
-0.09103099256753922,
-0.05056575685739517,
0.05001315474510193,
-0.10138006508350372,
-0.0454280711710453,
-0.058248620480298996,
-0.001918111927807331,
-0.008219100534915924,
0.012925194576382637,
-0.1622626781463623,
0.06851723045110703,
-0.08... | 0.077254 |
# Affinity Assistant [Specifying `Workspaces` in a `Pipeline`](../workspaces.md#specifying-workspace-order-in-a-pipeline-and-affinity-assistants) explains how an affinity assistant is created when a `persistentVolumeClaim` is used as a volume source for a `workspace` in a `pipelineRun`. Please refer to the same section... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/affinity-assistant.md | main | tekton | [
-0.03639132156968117,
-0.041786711663007736,
-0.0041998629458248615,
0.05543766915798187,
0.011117812246084213,
-0.06963276863098145,
-0.01673584245145321,
-0.041093163192272186,
0.020929837599396706,
0.005595418158918619,
-0.018110185861587524,
0.01571773737668991,
-0.015263146720826626,
... | 0.178237 |
# API Versioning ## Adding a new API version to a Pipelines CRD 1. Read the [Kubernetes documentation](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/) on versioning CRDs, especially the section on [specifying multiple versions](https://kubernetes.io/docs/tasks... | https://github.com/tektoncd/pipeline/blob/main/docs/developers/api-versioning.md | main | tekton | [
-0.027585292235016823,
-0.002599122002720833,
0.044239409267902374,
-0.08877050131559372,
-0.03521209955215454,
0.0024608492385596037,
-0.08179610967636108,
0.000043017811549361795,
0.04377482086420059,
0.0019808977376669645,
0.009368961676955223,
-0.05257605016231537,
-0.05386501923203468,
... | -0.010585 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.