fix: plugin resolution for multi-projects support

[camilamacedo86]

Closes: #1526

Note that the problem was faced/found in the #1498. (the error is faced when we gen the testdata which is checked in the CI) In this way, it is easy verified by checking that the same PR is working successfully with this fix applied.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86

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

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

[camilamacedo86]

/assign @estroz

[estroz]

If I understand what you're doing here, I think these changes are conflating "use the latest plugin version that supports a given project version" with "allow multiple non-default plugins per project version". The latter problem is solved by permitting multiple plugins per project version, then resolving a plugin key to a single plugin or erroring out. See #1536.

[camilamacedo86]

HI @estroz,

If I understand what you're doing here, I think these changes are conflating "use the latest plugin version that supports a given project version" with "allow multiple non-default plugins per project version".

It will return always the latest plugin version which is supported by the PROJECT version.

Example
We have:

• go.kubebuilder.io/v2.0.0 which is supported by V2 and V3
• go.kubebuilder.io/v3.0.0 which is supported by V3

Then:

• When I run the KB commands for V2 PROJECT version the upper plugin versions which are supported by V2 projects be used. In this case is: go.kubebuilder.io/v2.0.0
• When I run the KB commands for V3 PROJECT version the upper plugin version which is supported by V3 projects be used. In this case is: go.kubebuilder.io/v3.0.0

And then, if we implement a new version such as go.kubebuilder.io/v3.1.0 then, it will be the default version returned/used by V3.

I hope that it clarifies.

[camilamacedo86]

Closing this one based in the comment: #1526 (comment)

[k8s-ci-robot]

@camilamacedo86: PR needs rebase.

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.