⚠️ Go module fullfillment for v2+

[Adirio]

Targets #1791 for future versions

Fixes: #1562

It is not technically a breaking change but requires action from third-parties.

[Adirio]

/cc @droot @DirectXMan12 @mengqiy WDYT?

[camilamacedo86]

Since the next release will be 3.0.0 and we cannot so longer push a patch release from master anyway then, IMO all here should be v3instead of v2. Otherwise, I am ok with the changes made.

c/c @pwittrock @estroz @DirectXMan12 wdyt?

[Adirio]

Are we 100% certain next kubebuilder version is going to be 3.0.0? (Remember that I'm not talking about neither the kubebuilder base plugins nor the project configuration file version.)

I think that we are probably going to go to v3.0.0 next, but that there is still a chance to get a kubebuilder v2.4.0 version, and that's what I think that we should first bump to v2, and open an issue to track the change for the v3 milestone. It is just a search and replace at the end. The hard part is rebasing when files are moved.

[estroz]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Adirio, estroz

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 [estroz]

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

[Adirio]

I think that with #1798 tracking the change to v3, this can be merged. It requires lgtm.

[camilamacedo86]

/lgtm