Refine and pick a proper log verbosity level for CPI

[zhanggbj]

What would you like to be added?

While debugging CPI, we noticed some log levels are too small and generate overwhelming logs which is not helpful and noisy. We need to follow that k8s community logging best practice to refine and pick a proper log level for CPI code.

Why is this needed?

For e.g., as default log level is 1, everytime Instance() interface is called, a log is generated as below, we should set it to debug log level like 4.

I0416 08:18:02.863769       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:18:02.864222       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:18:02.865114       1 cloud.go:175] Enabling load balancer support in vsphere paravirtual cloud provider
I0416 08:18:02.968486       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:18:03.076458       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:23:03.150701       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:23:03.280804       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:28:03.394268       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:28:03.526673       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:33:03.624287       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:33:03.750358       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:38:03.866328       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider
I0416 08:38:03.959358       1 cloud.go:182] Enabling Instances interface on vsphere paravirtual cloud provider

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[zhanggbj]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten