add kubernetes-verify-go-licenses-periodical job

[Priyankasaggu11929]

What this PR does / why we need it:

The PR adds a periodic job ci-kubernetes-verify-go-licenses , to partly address the asks from the Issue kubernetes/kubernetes#108942 (comment):

We need to monitor all kubernetes repos for (At least start with k/k)

• the licenses of dependencies listed in go.mod are valid ( https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md )
• ensure the project continues to use a license that is valid for us over time
• ensure that the dependency is still active/available for us to use.

Which issue(s) this PR fixes:

Part of the fix for kubernetes/kubernetes#108942

[Priyankasaggu11929]

/hold

Remove hold after PR kubernetes/kubernetes#109299 is merged

[Priyankasaggu11929]

@dims, This is WIP PR for the verify-licenses periodic job.

I need information on the following bits:

• Do we want to add the job as canary first?
• What needs to be the job interval (6 hours) & what build cluster to be used - k8s-infra-prow-build?
• Whether/not to add Testgrid dashboard/tabs/alert-emails information?
• I'm not sure about what the Environment variables in the other similar jobs means? Need help identifying the required ones here.
• What resource limits/requests to be set?

[dims]

/assign @MadhavJivrajani @nikhita

[dims]

@Priyankasaggu11929 can we please revive this? looks like make verify-yamllint fails

line 149 and column 54 probably?

config/jobs/kubernetes/sig-testing/verify.yaml
  149:54    error    trailing spaces  (trailing-spaces)

[Priyankasaggu11929]

Hello @dims, actually I was waiting on some information on the bits here #26220 (comment)

When last I checked the failing test logs, it was complaining for adding testgrid dashboards meta. I will revise the PR tomorrow (my morning).

Just need help in confirming the information bits in the above comment? Thank you!

[dims]

• Do we want to add the job as canary first?

No, let's do the same as we did with check-dependency-stats-periodical

• What needs to be the job interval (6 hours) & what build cluster to be used - k8s-infra-prow-build?

6 Hours is good. we don't really care which cluster this runs in, leave it empty

• Whether/not to add Testgrid dashboard/tabs/alert-emails information?

Add the minimum required to pass verification

• I'm not sure about what the Environment variables in the other similar jobs means? Need help identifying the required ones here.

Start with similar to check-dependency-stats-periodical, if things fail, we can try to fix it (don't worry about those env vars)

• What resource limits/requests to be set?

check-dependency-stats-periodical doesn't set any, so we should leave it alone

[Priyankasaggu11929]

/unhold

[Priyankasaggu11929]

@dims, updated the PR. PTAL. Thank you! 🙂

[dims]

Let's give it a shot!

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, Priyankasaggu11929

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:

• config/OWNERS [dims]

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

[k8s-ci-robot]

@Priyankasaggu11929: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key verify.yaml using file config/jobs/kubernetes/sig-testing/verify.yaml

In response to this:

What this PR does / why we need it:

The PR adds a periodic job ci-kubernetes-verify-go-licenses , to partly address the asks from the Issue kubernetes/kubernetes#108942 (comment):

We need to monitor all kubernetes repos for (At least start with k/k)

• the licenses of dependencies listed in go.mod are valid ( https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md )
• ensure the project continues to use a license that is valid for us over time
• ensure that the dependency is still active/available for us to use.

Which issue(s) this PR fixes:

Part of the fix for kubernetes/kubernetes#108942

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.