bitnami/external-dns --- how to form fqdnTemplate with Values...

[chris8205]

Name and Version

bitnami/external-dns

What architecture are you using?

amd64

What steps will reproduce the bug?

i would like to do something like this..

global:
  domain: mydomain.tld

external-dns:
  fqdnTemplates:
    - {{`{{.Name}}.{{.Namespace}}`}}.{{ .Values.global.domain }}

At the end I would like to get template names like

MyService.MyNamespace.mydomain.tld

Are you using any custom parameters or values?

think something like this...

  fqdnTemplates:
    - {{`{{.Name}}.{{.Namespace}}`}}.{{ .Values.global.domain }}

What is the expected behavior?

--fqdnTemplate={{.Name}}.{{.Namespace}}.mydomain.tld

What do you see instead?

--fqdnTemplate={{`{{.Name}}.{{.Namespace}}`}}.{{ .Values.global.domain }}

[carrodher]

Hi, the issue may not be directly related to the Bitnami Helm chart, but rather to how the application or Helm is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance.

If you have any questions about the application, customizing its content, or using technology and infrastructure, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.