📖 update prerequisites to clarifies go versions which are supported

[camilamacedo86]

Description
📖 Update go version information in the QuickStart Prerequisites

Motivation
Closes: #2543

[coderanger]

-1 on making this so specific. We can certainly recommend versions that are tested with but I don't think this reflects the reality of what versions are supported.

[camilamacedo86]

Hi @coderanger,

We can only support these specific versions. We do not test all ensure it with all versions.
Unfortunately, the project does not work in many scenarios when users do not use the supported Golang versions since it has break changes. E.g. Go 1.18 will not work with the latest release at all since go get was deprecated and no longer available in 1.18. KB and SDK never provided support to a big matrix and we only officially supported one Golang version per release always. But from golang1.13 to 1.15 ( e.g.), we were not impacted which is not the case with these latest Golang releases.

These are the versions that we can support now, however, users still able to use any other version as please them.
We just need to clarify how it works currently. But we are open to any proposal for a design solution that would allow us to support a bigger matrix of go versions in the future as well. Then, IHMO that needs to be proposed via doc design where will be highlighted how we will achieve and ensure it.

So examples of the issues and scenarios to illustrate it:

• Cannot scaffold with Go 1.16 #2172
• To began to support Go 1.16: [META] Go 1.16 #2067
• "kubebuilder init" command changed go 1.15 in go mod becomes 1.16  #2292
• Initializing a project does not work with 3.3.0 #2488
• Kubebuilder inits in go1.16 and pkgs miss methods later on #2518
• "kubebuilder create api" does not work with Go 1.18 #2543

I hope that clarifies.

[AlmogBaku]

I'm with @camilamacedo86 here. Declaring the versions which are supported means that this is what the team has identified as potentially broken. You are always welcome to challenge it, but this is not what we recommend.

/lgtm

[k8s-ci-robot]

@AlmogBaku: changing LGTM is restricted to collaborators

In response to this:

I'm with @camilamacedo86 here. Declaring the versions which are supported means that this is what the team has identified as potentially broken. You are always welcome to challenge it, but this is not what we recommend.

/lgtm

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AlmogBaku, 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]

By thinking deeper here.
Why we are adding the min/ max go version for each bin released?
In the doc we try to keep the state/info only about the latest release/master

So, that makes no sense. We actually should only have now GO >= 17 and <=18
We are bumping GO 1.18 so we might solve this scenario.

c/c @AlmogBaku