feature: give users control over controller verbosity

[MikeSpreitzer]

Feature Description

The controller programs have command line flags for controlling their logging verbosity, but users do not currently have any control over that. Users should be able to control the logging verbosity of the controllers.

Proposed Solution

There are multiple layers to content with here, and different kinds of layers.

The easy case is Helm charts. They are parameterized and the parameters have default values.

A harder case is KubeFlex PostCreateHooks. In KubeFlex release 0.5.0 and later these can be parameterized, but they have no concept of default values.

There is also the ginkgo-based test.

There are also GitHub Actions workflows.

Want to contribute?

• I would like to work on this issue.

Additional Context

No response

[MikeSpreitzer]

PR #2041 addressed the kubestellar-controller-manager HelmChart and the bash script for running test/e2e/multi-cluster-deployment.

[ezrasilvera]

@MikeSpreitzer Do you considered this as completed due to #2041 ? Maybe we should have different issues for unrelated (in terms of code) items (e.g., ginkgo) ?

[ezrasilvera]

Also can you please elaborate which aspect of the multiple items you consider as high priority ?

[MikeSpreitzer]

This is not done.
There is still more plumbing to be done.

Some of it involves unanswered design questions, see kubestellar/ocm-status-addon#57