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
This commit removes the `EmbeddedStatus` feature flag. It removes all
the test cases related with the `full` and `both` `EmbeddedStatus` and
only kept the `minimal` test cases as default.
In detail, the test cases that checks the `taskruns` or `runs` status from
previous was changed to checking referenced `taskruns` or `runs` from
the `ChildReferences`.
Copy file name to clipboardExpand all lines: docs/install.md
-6
Original file line number
Diff line number
Diff line change
@@ -475,11 +475,6 @@ The default is `false`. For more information, see the [associated issue](https:/
475
475
most stable features to be used. Set it to "alpha" to allow [alpha
476
476
features](#alpha-features) to be used.
477
477
478
-
- `embedded-status`: set this flag to "full" to enable full embedding of `TaskRun` and `Run` statuses in the
479
-
`PipelineRun`status. Set it to "minimal" to populate the `ChildReferences` field in the `PipelineRun` status with
480
-
name, kind, and API version information for each `TaskRun` and `Run` in the `PipelineRun` instead. Set it to "both" to
481
-
do both. For more information, see [Configuring usage of `TaskRun` and `Run` embedded statuses](pipelineruns.md#configuring-usage-of-taskrun-and-run-embedded-statuses).
482
-
483
478
- `resource-verification-mode`: Setting this flag to "enforce" will enforce verification of tasks/pipeline. Failing to verify will fail the taskrun/pipelinerun. "warn" will only log the err message and "skip" will skip the whole verification.
484
479
- `results-from`: set this flag to "termination-message" to use the container's termination message to fetch results from. This is the default method of extracting results. Set it to "sidecar-logs" to enable use of a results sidecar logs to extract results instead of termination message.
485
480
@@ -526,7 +521,6 @@ Features currently in "alpha" are:
-[Cancelling a <code>PipelineRun</code>](#cancelling-a-pipelinerun)
39
38
-[Gracefully cancelling a <code>PipelineRun</code>](#gracefully-cancelling-a-pipelinerun)
@@ -1389,21 +1388,6 @@ Your `PipelineRun`'s `status` field can contain the following fields:
1389
1388
- `finallyStartTime`- The time at which the PipelineRun's `finally` Tasks, if any, began
1390
1389
executing, in [RFC3339](https://tools.ietf.org/html/rfc3339) format.
1391
1390
1392
-
### Configuring usage of `TaskRun` and `Run` embedded statuses
1393
-
1394
-
Currently, the default behavior is to pupulate `status.childReferences` with references to the `TaskRun`s and
1395
-
`Run`s, which can be used to look up their statuses.
1396
-
1397
-
This behavior can be controlled by changing the `embedded-status` feature flag in the `feature-flags`
1398
-
config map. See [`install.md`](./install.md#customizing-the-pipelines-controller-behavior) for more
1399
-
information on feature flags. The possible values for `embedded-status` are:
1400
-
- `minimal`- The current default behavior, populate `status.childReferences`, not `status.taskRuns` or `status.runs`.
1401
-
- `full`- Populating `status.taskRuns` and `status.runs`, without populating `status.childReferences`.
1402
-
- `both`- Populate `status.childReferences` as well as `status.taskRuns` and `status.runs`.
1403
-
1404
-
*Note that after the `PipelineRunStatus` migration as planned in [TEP-100](https://github.com/tektoncd/community/blob/main/teps/0100-embedded-taskruns-and-runs-status-in-pipelineruns.md#2-deprecate-and-remove-full-embedded-status),
1405
-
[the `full` and `both` `embedded-status` options will be removed](https://github.com/tektoncd/pipeline/blob/main/docs/deprecations.md).
1406
-
1407
1391
### Monitoring execution status
1408
1392
1409
1393
As your `PipelineRun` executes, its `status` field accumulates information on the execution of each `TaskRun`
0 commit comments