Value Statement

Currently, we enable the debug mode by default. sometimes, we found that the useful logs can be flushed out. so we want to disable the debug logs by default. But we need to implement a way for user to enable the debug at runtime

Definition of Done for Engineering Story Owner (Checklist)

• update the manifests to disable debug by default - DONE
• Ask SRE to update their manifest as well - DONE
• introduce a configmap to enable debug at runtime. refer to this investigation result for implementation – https://github.com/stolostron/multicluster-global-hub/issues/1178
• use zaper in maestro side so that it can be configurable at runtime.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.