Add support to add labels and annotations to build pod

[wanjunlei]

Signed-off-by: wanjunlei wanjunlei@kubesphere.io

Changes

This pr adds two fields labels and annotations to the Build and BuildRun CRD, the controller will add the labels and annotations to the taskrun, and eventually be added to the build pod.

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Add support to add labels and annotations to build pod

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign heavywombat for approval by writing /assign @heavywombat in a comment. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[oops-oom]

Maybe we should just label build and buildrun, and let pod inherit labels from build and buildrun as #625 #1069

[SaschaSchwarze0]

Thanks for engaging @wanjunlei

In Shipwright, we often distinguish two personas: build strategy authors and build users. Build strategy authors define which steps need to be performed to reach a certain behavior. Pod annotations often cause a behavior, for example kubernetes.io/ingress-bandwidth (network traffic shaping). Build users should not necessarily gain control over such behaviors.

Because of this, we already have the capability to propage annotations from build strategies to taskruns, but not from builds or buildruns. See Propagating annotations from the build strategy to the pod.

Similarly, there is effort in progress related to labels, and here to also include a propagation for Build users.

We invite you to join our community meeting, https://github.com/shipwright-io/community#how-can-i-get-involved.

In general, every API change requires an enhancement proposal, which we call SHIPs.

/hold