Enable additional linters

[sedefsavas]

Follow-up issue to #2414

Enable the following linters:

• stylecheck
• errcheck
• gosec

Also, these are some relevant PRs in cluster-api repo. We should compare what we have with the ones added there.
kubernetes-sigs/cluster-api#4649
kubernetes-sigs/cluster-api#4624
kubernetes-sigs/cluster-api#4657
kubernetes-sigs/cluster-api#4631
kubernetes-sigs/cluster-api#4697

/good-first-issue
/milestone Next

[k8s-ci-robot]

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

Please ensure the request meets the requirements listed here.

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:

Follow-up issue to #2414

Enable the following linters:

• stylecheck
• errcheck
• gosec

Also, these are some relevant PRs in cluster-api repo. We should compare what we have with the ones added there.
kubernetes-sigs/cluster-api#4649
kubernetes-sigs/cluster-api#4624
kubernetes-sigs/cluster-api#4657
kubernetes-sigs/cluster-api#4631
kubernetes-sigs/cluster-api#4697

/good-first-issue
/milestone Next

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.

[JacekDuszenko]

Hey, I'd like to have a try on this task :)
/assign @JacekDuszenko

[tech-geek29]

Hi @JacekDuszenko are you still working on this or can I assign it to myself? I have done the relevant changes and can raise a PR!

[JacekDuszenko]

Sure, go for it if you want to, I'm working on sth else right now @tech-geek29

[tech-geek29]

/unassign @JacekDuszenko
/assign

[tech-geek29]

@sedefsavas:Does this issue still needs to be kept open?

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle rotten

[randomvariable]

This is fixed I think
/close

[k8s-ci-robot]

@randomvariable: Closing this issue.

In response to this:

This is fixed I think
/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.