🌱 Enable requiredfields linter

[sivchari]

What this PR does / why we need it:

Part of #11834

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/area api

[JoelSpeed]

I think best to leave the config "shadow" so that we can see what we could configure if we decided to change

[sivchari]

Fixed!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[JoelSpeed]

Would be good to squash the commits for this PR, but otherwise LGTM

[sivchari]

Should I summarize the commits ?

[JoelSpeed]

I think in this case we don't need the individual history of the changes on this branch. I'd encourage us to try and keep commits atomic. So if we are making fixups later, lets squash those into the commits earlier in the branch that introduced the bit that needed fixing (eg in this case, the first commit added some unwanted indentation, the second puts it back to how it was before, we should squash 2 into 1 here)

[sivchari]

Okay!

[sbueringer]

On these kind of PRs I would expect just one commit. I'm also fine in general with just squashing via Prow if the first commit has an appropriate title

[chrischdi]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 1c3db99f4ded2ba33ae24c6ce3b4a6aa51458d5f

[sbueringer]

Needs rebase.

Let's go ahead and merge this PR after rebase. But I would expect once we add required markers in the other PR this linter might show some findings in v1beta1. They should then be ignored (on that other PR)

[k8s-ci-robot]

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