Background

We would like new code going into the CAPI operator repository to be linted based on the teams linting standards.

The CPMS is a good source for an initial configuration, though may be a touch strict, we can make a judgement if we want to disable some of the linters it uses for this project.

Some linters enabled may be easy to bulk fix in the existing code, others may be harder.

We can make a judgement as to whether to fix the issues or set the CI configuration to only check new code.

Steps

• Copy CPMS golangci-lint configuration over
  • https://github.com/openshift/cluster-control-plane-machine-set-operator/blob/main/.golangci.yaml
• Evaluate and adjust the CI config as necessary
• Make a judegment on whether to fix or ignore existing failures
  • Maybe set to only new code linted

Stakeholders

• Cluster infra

Definition of Done

• As we create PRs to the CAPI operator repo, linting feedback is given

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>