external-dns icon indicating copy to clipboard operation
external-dns copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

fqdn template expansion doesn't work for multiple fields on `node` endpoints.

Open jordo opened this issue 2 years ago • 6 comments

What happened:

fqdn template expansion doesn't work for multiple fields on node endpoints. It just grabs the first one at index 0.

What you expected to happen:

Multiple endpoints should be created

How to reproduce it (as minimally and precisely as possible):

Specify multiple fqdnTemplate via comma separated list

Anything else we need to know?:

Environment:

  • External-DNS version (use external-dns --version):
  • DNS provider:
  • Others:

jordo avatar Feb 14 '23 18:02 jordo

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar May 15 '23 19:05 k8s-triage-robot

/remove-lifecycle stale

jordo avatar May 15 '23 21:05 jordo

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 20 '24 12:01 k8s-triage-robot

/remove-lifecycle stale

Cubixmeister avatar Jan 20 '24 15:01 Cubixmeister

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Apr 19 '24 15:04 k8s-triage-robot

/remove-lifecycle stale

jordo avatar Apr 19 '24 16:04 jordo

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 18 '24 17:07 k8s-triage-robot

/remove-lifecycle stale

jordo avatar Jul 18 '24 18:07 jordo

Any updates on this issue? This bug may force us to run multiple external-dns replicas only to have multiple records per node.

fredrikgh avatar Sep 10 '24 10:09 fredrikgh