Skip to content

externaldns.interval not being respect #1676

Closed
@zyue110026

Description

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions