Skip to content

fix/external-dns-cloudflare-api-token #2916

@vaheed

Description

@vaheed

Describe the bug:
otomi apply fails when External-DNS is enabled with the Cloudflare provider. The Helm values template external-dns-raw.gotmpl references a non-existent field .apiSecret, while the Helm schema and documentation define the Cloudflare credential as .apiToken. This causes template rendering to fail and blocks installation.

To Reproduce
Steps to reproduce the behavior:
Helm Install APL-Core v4.13.1

Expected behavior: (a clear and concise description of what you expected to happen)
failed to render values files "../values/external-dns/external-dns-raw.gotmpl":
executing "stringTemplate" at <.apiSecret>: map has no entry for key "apiSecret"

Screenshots: (if applicable, add screenshots to help explain your problem)
Not applicable (CLI error).

Cluster(s):
Cloud: self-managed / on-prem (talos based on this guide )

Additional context:
The Cloudflare External-DNS configuration in values/external-dns/external-dns-raw.gotmpl expects .apiSecret, but the Helm values schema and External-DNS documentation use .apiToken. Replacing .apiSecret with .apiToken (and setting CF_API_TOKEN) resolves the issue. This appears to be a template bug in APL-Core v4.13.1.
What's wrong: The /values/external-dns/external-dns-raw.gotmpl template file at line 44 is trying to access .apiSecret for the Cloudflare provider, but the Helm schema defines the field as .apiToken. This is a bug in APL-Core v4.13.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions