DeliverySpec.Timeout on Broker and Trigger

[pierDipi]

Fixes #5654

Proposed Changes

• Preserve unknown fields on trigger.spec.delivery
• Add test for broker and trigger using spec.delivery.timeout

Pre-review Checklist

• At least 80% unit test coverage
• E2E tests for any new behavior
• Docs PR for any user-facing impact
• Spec PR for any new API feature
• Conformance test for any change to the spec

Release Note

Trigger accepts a timeout field in its delivery parameters `spec.delivery.timeout`

[knative-prow-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[pierDipi]

/test all

[codecov]

Codecov Report

Merging #5687 (0a00df5) into main (00ab8a1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #5687   +/-   ##
=======================================
  Coverage   82.68%   82.68%           
=======================================
  Files         200      200           
  Lines        6261     6261           
=======================================
  Hits         5177     5177           
  Misses        750      750           
  Partials      334      334           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 00ab8a1...0a00df5. Read the comment docs.

[pierDipi]

/cherry-pick release-0.25

[knative-prow-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-0.25 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-0.25

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pierDipi]

/cherry-pick release-0.24

[knative-prow-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-0.24 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-0.24

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[matzew]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew, pierDipi

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [matzew,pierDipi]

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

[knative-prow-robot]

@pierDipi: new pull request created: #5689

Details

In response to this:

/cherry-pick release-0.25

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[knative-prow-robot]

@pierDipi: new pull request created: #5690

Details

In response to this:

/cherry-pick release-0.24

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.