add kube api linter

[fabian4]

What type of PR is this?

feat(lint): add kube api linter

What this PR does / why we need it:

add kube api linter

Which issue(s) this PR fixes:

Fixes #6546

Release Notes: Yes/No

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.29%. Comparing base (c853061) to head (576b18b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7303      +/-   ##
==========================================
- Coverage   72.29%   72.29%   -0.01%     
==========================================
  Files         231      231              
  Lines       34084    34084              
==========================================
- Hits        24641    24640       -1     
+ Misses       7670     7669       -1     
- Partials     1773     1775       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[fabian4]

For now just added few linters to integrate the ci workflow:

• "conditions"
• "nodurations"
• "nonullable"
• "notimestamp"
• "statusoptional"

We call adjust the linters later according to the community need.
👉 https://github.com/kubernetes-sigs/kube-api-linter/blob/main/docs/linters.md

[arkodg]

cc @rikatz for additional guidance

[arkodg]

thanks @fabian4 , had a few questions

• curious why the non /api file fixes were needed
• can you enable all, add the failures in a GH issue, so we can make sure to enable all and fix the issues

[fabian4]

Hi @arkodg

• With the dependency upgrade 'mvdan/gofumpt' causes the failed test.
  • https://github.com/mvdan/gofumpt/releases/tag/v0.9.0
  • Proposal: Clothe naked returns mvdan/gofumpt#285
• For the current kube api liner, we already enable the linter to pass the test. As for the rest, I think we may need some extra effort to fix it all according to the result I ran locally. Also I think some of the linters still need discussion which we can do it in another pr.

[zirain]

@fabian4 It would be better if you can move those unrelated changes to a separated PR and rebase this one after it merged.
it will keep this PR as clean as enough.

[zirain]

wait #7484

[arkodg]

LGTM thanks

[zirain]

/retest