externaldns.interval not being respect
zyue110026 opened this issue · 0 comments
zyue110026 commented
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.
externaldns.interval does not take affect when change it to other values. This is because missing implementation for this value in external-dns/external-dns.yaml file:
Expected Behavior
Change externaldns.interval to other value can take effect
Actual Behavior
Only default value '1m' take effect