[Bug]: tls.Config should use VerifyConnection #10477

Is there an existing issue already for this bug?

• I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

• I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

• I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

1.29 (latest patch)

What version of Kubernetes are you using?

1.35

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

The new golangci-lint 2.11.4 detects a valid error, we're using a custom VerifyPeerCertificate but we don't have VerifyConnection, this could bypass the custom verify connection, this shouldn't be an issue but it's good to have the same method in both places to avoid confusions or add security problems in the future

Cluster resource

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct