cla: Switch over to EasyCLA

[MadhavJivrajani]

This makes the required changes needed to support EasyCLA
after it has been fully migrated:

• Change the context checked from cla/linuxfoundation to EasyCLA
• Update tests to reflect the changed context
• Remove bot comment in case the CLA is not signed and default
  to the EasyCLA bot's message.
• Change prow config to not treat EasyCLA as an optional context
  anymore. Add cla/linuxfoundation as the optional context and
  leave it there for an additional release cycle after EasyCLA
  is fully rolled out.

/area github-management
/sig contributor-experience
/assign @mrbobbytables @cblecker @nikhita
/hold

[MadhavJivrajani]

/cc @spiffxp

[MadhavJivrajani]

@mrbobbytables are the links mentioned for support in the bot message the same for EasyCLA as well?

test-infra/prow/plugins/cla/cla.go

Lines 39 to 50 in cd3e975

	:memo: **Please follow instructions at <https://git.k8s.io/community/CLA.md#the-contributor-license-agreement> to sign the CLA.**
	It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
	---
	- If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your [email is set on your git commits](https://help.github.com/articles/setting-your-email-in-git/).
	- If you signed the CLA as a corporation, please sign in with your organization's credentials at <https://identity.linuxfoundation.org/projects/cncf> to be authorized.
	- If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: <https://support.linuxfoundation.org/>
	- Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]
	<!-- need_sender_cla -->

[cblecker]

/uncc @petr-muller @spiffxp
/assign

[mrbobbytables]

I'm actually wondering if we want to have our own message at all - EasyCLA itself posts direct links to sign the CLA and support details. The one thing that our docs do have that theirs don't is updating affiliation and how to retrigger a check (/check-cla or for easycla /easycla) @cblecker @nikhita @alisondy what do you think?

Here is a screenshot of what it looks like:

[alisondy]

the provided message lgtm so /shrug

but yeah the resigning cla stuff will need to be looked into

[cblecker]

Yeah I'm not sure how much value we get by adding another comment, so maybe we disable that?

[mrbobbytables]

Yeah I'm not sure how much value we get by adding another comment, so maybe we disable that?

Yeah, I think we just remove it at this point

[MadhavJivrajani]

I've created a new commit for removing the bot message: da7f147
Will squash when things look good :)

[mrbobbytables]

/lgtm
👍

[dims]

/approve

[cblecker]

One comment, otherwise LGTM.

@MadhavJivrajani Once addressed, would you mind squashing? Thanks!

/lgtm cancel

[MadhavJivrajani]

@cblecker made the changes and squashed, thanks!
PTAL :)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, dims, MadhavJivrajani, stevekuznetsov

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 [cblecker,dims,stevekuznetsov]
• prow/OWNERS [cblecker,stevekuznetsov]

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

[mrbobbytables]

/hold cancel

[k8s-ci-robot]

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

• key config.yaml using file config/prow/config.yaml

In response to this:

This makes the required changes needed to support EasyCLA
after it has been fully migrated:

• Change the context checked from cla/linuxfoundation to EasyCLA
• Update tests to reflect the changed context
• Remove bot comment in case the CLA is not signed and default
  to the EasyCLA bot's message.
• Change prow config to not treat EasyCLA as an optional context
  anymore. Add cla/linuxfoundation as the optional context and
  leave it there for an additional release cycle after EasyCLA
  is fully rolled out.

/area github-management
/sig contributor-experience
/assign @mrbobbytables @cblecker @nikhita
/hold

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.