external-dns
external-dns copied to clipboard
Using the `txtSuffix` field in the helm chart does nothing
What happened:
I set the txtSuffix and txtPrefix but only the txtSuffix shows up when I render the YAML.
What you expected to happen: I would expect both to show.
How to reproduce it (as minimally and precisely as possible):
values.yaml:
provider:
name: cloudflare
env:
- name: CF_API_TOKEN
valueFrom:
secretKeyRef:
name: external-cf-secrets
key: CF_API_TOKEN
txtPrefix: "test-prefix"
txtSuffix: "test-suffix"
txtOwnerId: "testing"
relevant lines from the deployment.yaml:
args:
- --log-level=info
- --log-format=text
- --interval=1m
- --source=service
- --source=ingress
- --policy=upsert-only
- --registry=txt
- --txt-owner-id=testing
- --txt-prefix=test-prefix
- --provider=cloudflare
Anything else we need to know?:
Using the latest version of the helm chart 1.14.5,
Environment:
- External-DNS version (use
external-dns --version):v0.14.2 - DNS provider:
cloudflare,ns1
Update, I reviewed the code for the helm chart here:
{{- if and (eq .Values.txtPrefix "") (ne .Values.txtSuffix "") }}
- --txt-suffix={{ .Values.txtSuffix }}
{{- end }}
It will work if I set txtPrefix: "" but not if its not set. If this is intended we can close this issue but this seems strange to me since both values default to nil
@jmtx1020 it mentioned in its description that txtSuffix and txtSuffix are mutually exclusive. so it seems correct
Hey @kundan2707 ,
We can close this issue if it's meant to work that way but it seemed weird to have to set something to "" to make the other work.
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
Not stale. If the default value is used for txtPrefix, but you explicitly set the txtSuffix, then txtSuffix doesn't render because txtPrefix by default is not an "".
Here's some examples:
# values.yaml
txtSuffix: test
helm template external-dns/external-dns --version 1.14.3 --values values.yaml
args:
- --log-level=info
- --log-format=text
- --interval=1m
- --source=service
- --source=ingress
- --policy=upsert-only
- --registry=txt
- --provider=aws
helm template external-dns/external-dns --version 1.13.0 --values values.yaml
args:
- --log-level=info
- --log-format=text
- --interval=1m
- --source=service
- --source=ingress
- --policy=upsert-only
- --registry=txt
- --txt-suffix=test
- --provider=aws
In fact, this was a breaking change for us since we didn't provide txtPrefix, but set txtSuffix. Many of our records started to collide after we upgraded the helm chart.
/remove-lifecycle stale
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
/lifecycle frozen