[cinder-csi-plugin] implement structured logging

[sergelogvinov]

What this PR does / why we need it:

implement structured logging KEP 1602

CSI plugins often use common values like node name, volume name, volume ID, and instance ID in unstructured error and log messages. This makes it hard to group and sort them. I want to change these logs to structured logs, as the core Kubernetes team has decided to move in this direction

Current logs:

CreateVolume: Successfully created volume 47d323fd-b06c-424e-b27b-d27db2fb2c5c in Availability Zone: nova of size 10 GiB

Structured logs

"CreateVolume() successfully created" volumeID="aaae827a-f724-419f-8864-ec4aa7ba9776" size=10 zone="nova" cloud=""

Which issue this PR fixes(if applicable):

make sense after #2640

Special notes for reviewers:

Release note:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kayrus for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @sergelogvinov. Thanks for your PR.

I'm waiting for a kubernetes 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.

[jichenjc]

/ok-to-test

[k8s-ci-robot]

@sergelogvinov: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cloud-provider-openstack-test	4ea910a	link	true	/test pull-cloud-provider-openstack-test
pull-cloud-provider-openstack-check	4ea910a	link	true	/test pull-cloud-provider-openstack-check

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[kayrus]

@sergelogvinov thanks for the PR. Please add more context in the PR description, e.g. how logs will look like comparing to old style. Also its worth to add this link for the context https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/1602-structured-logging/README.md#new-klog-methods
The release notes are must have for such changes.

[k8s-ci-robot]

PR needs rebase.

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.