Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

externaldns.interval not being respect #1676

Closed
zyue110026 opened this issue Jul 30, 2024 · 0 comments · Fixed by #1677
Closed

externaldns.interval not being respect #1676

zyue110026 opened this issue Jul 30, 2024 · 0 comments · Fixed by #1677

Comments

@zyue110026
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant