Define clear log levels for troubleshooting

[MegaByte875]

Introduction

Occurs during the scale-in period.

E0921 21:50:42.200442       1 pvc.go:64] get PVC [test/storaged-log-nebula-storaged-16] failed: persistentvolumeclaims "storaged-log-nebula-storaged-16" not found
E0921 21:50:42.204379       1 pvc.go:64] get PVC [test/storaged-data-nebula-storaged-16] failed: persistentvolumeclaims "storaged-data-nebula-storaged-16" not found
I0921 21:50:45.231263       1 nebulacluster.go:119] NebulaCluster [test/nebula] updated successfully
I0921 21:50:45.231291       1 nebula_cluster_controller.go:173] NebulaCluster [test/nebula] reconcile details: waiting for nebulacluster ready
I0921 21:50:45.231297       1 nebula_cluster_controller.go:143] Finished reconciling NebulaCluster [test/nebula] (3.15077667s), result: {false 10s}

The logs should be output at the debug level, but they are output at the info level, which confuses users. Contents

Related work

[galbwe]

Hi. Can I work on this issue?

[wey-gu]

Dear @galbwe ,

Sorry, after checking with @MegaByte875 ,it's known that this work was already started from his side... Extremely sorry about that.

Are you interested in this task: https://github.com/vesoft-inc/nebula-operator/issues/205 instead, we could break down it into multiple subtasks.

The studio now has a single-container workload and could be an optional resource for the operator.

Thanks!