ci/gomod: added CI steps to check Golang directive

[mtulio]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Introduce CI step to validate the Go directive is according to the standard used in kubernetes project (ending with .0, x.y.0).

The step introduces the command verify-go-directive which will use a common script from cluster-api project to verify the directive is in conformance with the project standard.

Please leave a comment with your thoughts of which option would be ok to follow the practice by this project.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

The command is executed both in Github Actions and Prow, where Github Actions is handling correctly the exit code.

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

This issue is currently awaiting triage.

If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[mtulio]

/test all

[elmiko]

this makes sense to me

[mtulio]

I just added one more option to validate 'go.mod dotzero' using cluster-api practice, which would be preferred as shares practices from other kube projects (suggested by @damdo, TY). PTAL, would love to hear thoughts which path to go.

[mtulio]

/test pull-cloud-provider-aws-check

[mtulio]

pull-cloud-provider-aws-check is not reporting as expected, the new make command failed and it report as pass: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/cloud-provider-aws/1283/pull-cloud-provider-aws-check/1981728404394741760#1:build-log.txt%3A143

Suggested action items:

• (short) use make verify-go-directive on GHA
• (long) fix CI job to track exit code

[mtulio]

pull-cloud-provider-aws-check is not reporting as expected, the new make command failed and it report as pass: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/cloud-provider-aws/1283/pull-cloud-provider-aws-check/1981728404394741760#1:build-log.txt%3A143

Suggested action items:

• (short) use make verify-go-directive on GHA
• (long) fix CI job to track exit code

Not sure if I am looking at the correct place, looks like the runner have expected flags to fail

[mtulio]

/retest

[mtulio]

PR ready for review based in the step gomod-dotzero-check logs:

curl --retry 3 -fsL https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/refs/tags/v1.11.0/hack/verify-go-directive.sh | bash -s -- -g 1.24.0
Running go directive verify test for ./tests/e2e/go.mod
Running go directive verify test for ./go.mod

[damdo]

Thanks

/lgtm

[mtulio]

CI infra issues in job test.

/retest

[damdo]

/lgtm

[mtulio]

/retest

[mtulio]

/retest

[damdo]

/retest

[mtulio]

/retest

[elmiko]

/lgtm

[mtulio]

/retest

[mtulio]

Hey @kmala , what do you think of this check? Thanks!

/assign @kmala

[kmala]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kmala

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

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