chore: logging the service body when service controller invokes the cloud provider

[nilo19]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

/kind cleanup

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Release note:

chore: logging the service body when service controller invokes the cloud provider

[coveralls]

Coverage remained the same at 80.584% when pulling c6eec38 on nilo19:chore/log-port into 7160b8c on kubernetes-sigs:master.

[feiskyer]

This is useful for troubleshooting

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feiskyer, nilo19

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 [feiskyer,nilo19]

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

[MartinForReal]

/cherrypick release-1.0

[MartinForReal]

/cherrypick release-1.1

[k8s-infra-cherrypick-robot]

@MartinForReal: #778 failed to apply on top of branch "release-1.0":

Applying: chore: logging the service body when service controller invokes the cloud provider
Using index info to reconstruct a base tree...
M	pkg/provider/azure_loadbalancer.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/provider/azure_loadbalancer.go
CONFLICT (content): Merge conflict in pkg/provider/azure_loadbalancer.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: logging the service body when service controller invokes the cloud provider
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.0

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.

[k8s-infra-cherrypick-robot]

@MartinForReal: #778 failed to apply on top of branch "release-1.1":

Applying: chore: logging the service body when service controller invokes the cloud provider
Using index info to reconstruct a base tree...
M	pkg/provider/azure_loadbalancer.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/provider/azure_loadbalancer.go
CONFLICT (content): Merge conflict in pkg/provider/azure_loadbalancer.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: logging the service body when service controller invokes the cloud provider
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.1

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.