operator.scanSecretTTL not getting respect

[zyue110026]

We have noticed an instance of incorrect helming in one of your Kubernetes configuration files. Hardcoded or default configuration values in the template are considered anti-pattern and configurable values in the values.yaml file are not being respect, resulting in user-provided configurations never being applied. Additionally, we provide anecdotal evidence from trivy-operator#729 regarding the incorrect helming defect.

What steps did you take and what happened:

1. changing the operator.scanSecretTTL value to any value in values.yaml file.
2. using helm chart to deploy trivy operator
   [A clear and concise description of what the bug is, and what commands you ran.]

operator.scanSecretTTL does not take affect when changed to other values.

What did you expect to happen:

scanSecretTTL value should changed.

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

Environment:

• Trivy-Operator version (use trivy-operator version): main version
• Kubernetes version (use kubectl version):
• OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):