Promote onerror Tasks to beta

[chitrangpatel]

Changes

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Promote Ignore Task Failure to Beta

/kind feature

[vdemeester]

cc @afrittoli @JeromeJu

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[JeromeJu]

/lgtm

[pritidesai]

Thanks a bunch @chitrangpatel for this promotion. We are planning to utilize this feature in our deployment. While we are experimenting with this feature, we ran into the following limitation.

• Not able to access task's status (specifically reason) in finally tasks

tkn describes the list of taskRuns as expected:

🗂  Taskruns

 NAME                                                  TASK NAME       STARTED         DURATION   STATUS
 ∙ pipelinerun-with-failing-task-8lz7x-finish          finish          4 minutes ago   4s         Succeeded
 ∙ pipelinerun-with-failing-task-8lz7x-echo-fail       echo-fail       4 minutes ago   4s         Failed
 ∙ pipelinerun-with-failing-task-8lz7x-echo-continue   echo-continue   4 minutes ago   4s         Failed(FailureIgnored)

But in a finally task, how to distinguish between a failed task and a task with failure ignored.

At the time of designing onError feature at the step level, the step exit code is made available to subsequent steps. Similarly, we are looking for a way to classify a task which failed but with FailureIgnored.

[vdemeester]

@pritidesai we probably want to create a follow-up issue for this 👼🏼

[pritidesai]

@pritidesai we probably want to create a follow-up issue for this 👼🏼

#8110

Would this require a TEP? 😸

[chitrangpatel]

@pritidesai we probably want to create a follow-up issue for this 👼🏼

#8110

Would this require a TEP? 😸

I don't think a TEP will be required here since it's not adding new fields. It's providing access to existing fields via substitutions so I think we can probably justify it over an issue and implement it.