Remove log verbosity workaround when csi-addons supports -v=0

Currently, we set spec.driverSpecDefaults.log.verbosity: 3 in the csi-addons test script as a workaround because the zap logger in csi-addons v0.15.0 does not accept verbosity level 0.

File affected: tests/scripts/csiaddons.sh

Current workaround:

kubectl patch operatorconfig ceph-csi-operator-config -n rook-ceph --type merge -p '{"spec":{"driverSpecDefaults":{"deployCsiAddons":true,"log":{"verbosity":3}}}}'
kubectl patch operatorconfig ceph-csi-operator-config -n rook-ceph --type merge -p '{"spec":{"log":{"verbosity":3}}}'

Root Cause

The default spec.driverSpecDefaults.log.verbosity in OperatorConfig is 0, but csi-addons v0.15.0 uses the zap logger which rejects verbosity 0 with the error: Error: zap does not accept verbosity 0

Action Required

In the next csi-addons version:

1. Remove the log verbosity patches from tests/scripts/csiaddons.sh:
   • Remove or comment out the log verbosity setting in both patch commands
   • Keep only deployCsiAddons: true
2. Update the csi-addons version in:
   • deploy/examples/operator.yaml
   • deploy/examples/csi-operator.yaml
   • Documentation/Storage-Configuration/Ceph-CSI/ceph-csi-drivers.md
   • tests/scripts/csiaddons.sh
3. Test that the csi-addons container starts successfully with the default verbosity 0

Upstream Tracking

• Check csi-addons releases for fix: https://github.com/csi-addons/kubernetes-csi-addons/releases
• Verify zap logger fix in csi-addons codebase

Related

• Introduced in PR: #18366
• Fix: https://github.com/csi-addons/kubernetes-csi-addons/pull/1133