Logging is too silent by default when CSI driver is misconfigured

[ebblake]

I was trying to add this sidecar to my CSI driver, but my pod was stuck in a CrashLoopBackOff state. kubectl logs mydriverpod -c csi-health-monitor was unhelpful:

$ kubectl logs -n kubesan-system csi-controller-plugin-65776bcb7-68mm8 -c csi-health-monitor
I0116 18:48:15.917448       1 main.go:104] "Version" version="v0.14.0"
I0116 18:48:15.919201       1 common.go:143] "Probing CSI driver for readiness"
$ 

I traced it down to a missing advertisement of csi.ControllerServiceCapability_RPC_LIST_VOLUME_CONDITION in my ControllerGetCapabilities() gRPC call, but it took me adding a --v=2 argument to the command line of the sidecar.

Best practice when failing fast due to misconfiguration is to be verbose about what was misconfigured, rather than hiding it behind V(2), so that the logs can serve as a useful pointer for how to correct the misconfiguration.

[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

[ebblake]

/remove-lifecycle rotten