lets format the code in ci

[jayunit100]

@astoycos thinks were CRAZY bc we dont gofmt EVERY SINGLE PR

lets make him happy :)

files to impl

hack/verify-gofmt.sh
hack/update-gofmt.sh
https://github.com/kubernetes-sigs/kpng/blob/master/.github/workflows/vet-code.yml

[jayunit100]

/good-first-issue

[k8s-ci-robot]

@jayunit100:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[heisaman]

I'll fix it. 😃

[uablrek]

Please remember;

CI or any plugin MUST NOT update the repository itself!

It may seem like a cool idea but will come back and bite you in some way. Do as K8s, have a format test in CI that fails.

[uablrek]

For instance;
an update trigs an event -> the event updates the repo -> an update trigs an event -> ...

If you have more than one event that updates the code this is likely, and will ruin your day.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[knabben]

/remove-lifecycle stale

[gitvinit]

/assign

[abhishek44sharma]

@gitvinit are you working on this?

[gitvinit]

This should be done with PR: #485

[liangyuanpeng]

So this issue should be closed.

[gitvinit]

/close

[k8s-ci-robot]

@gitvinit: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

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.