k8s-triage-robot
commented
3 months ago 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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
vmax
What happened:
I'm developing a webhook provider. Underlying DNS provider rejects trying to create CNAME and TXT record of the same name (which abides by the RFC AFAIR). However I see that it attempts to create both old-style and new-style DNS TXT records:
test.example.com-->"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/default/test"cname-test.example.com-->"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/default/test"New-style records are created just fine (as they don't conflict with CNAME).
However, on the next run it still tries to create old-style records (as
txt/force-update:trueprovider-specific property has been assigned)What you expected to happen:
Registry is constructed from new-style records only; absence of old records is discarded
How to reproduce it (as minimally and precisely as possible):
WIP
Anything else we need to know?:
I believe the fix would be to either:
Environment:
external-dns --version):unknown(f5545b1e164776958fbb85ed055ae418fb0f24dc)