BUG FIX: fix log message when target group and cluster are in different VPCs

[zac-nixon]

Issue

n/a

Description

While testing out using a target group that belongs to a different vpc then the cluster, I noticed this error message. It's because the log message had 1 log string, then 3 args for k/v pairs. This fixes the log message to have the correct number of k/v pairs.

{"level":"dpanic","ts":"2024-10-30T18:40:02Z","msg":"odd number of arguments passed as key-value pairs for logging","ignored key":"vpc-0a7ef5bd8943067a8"}
{"level":"info","ts":"2024-10-30T18:40:02Z","msg":"registering endpoints using the targetGroup's vpcID","vpc-5ab15a27":"which is different from the cluster's vpcID"}

Checklist

• Added tests that cover your change (if possible)
• Added/modified documentation as required (such as the README.md, or the docs directory)
• Manually tested
• Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

• Backfilled missing tests for code in same general area 🎉
• Refactored something and made the world a better place 🌟

[k8s-ci-robot]

Hi @zac-nixon. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[shraddhabang]

/ok-to-test

[shraddhabang]

/lgtm
/approve

[M00nF1sh]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: M00nF1sh, shraddhabang, zac-nixon

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [M00nF1sh]

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

[shraddhabang]

/lgtm