Closed fenngineering closed 3 years ago
I have the same issue. After removing --godaddy-api-key
and --godady-api-secret
. I got the following error:
time="2021-02-20T20:57:45Z" level=fatal msg="flag parsing error: enum value must be one of aws,aws-sd,google,azure,azure-dns,hetzner,azure-private-dns,alibabacloud,clou
dflare,rcodezero,digitalocean,dnsimple,akamai,infoblox,dyn,designate,coredns,skydns,inmemory,ovh,pdns,oci,exoscale,linode,rfc2136,ns1,transip,vinyldns,rdns,scaleway,vul
tr,ultradns, got 'godaddy'"
The godaddy provider is not accepted by the --provider
flag.
In release v0.7.6
the corresponding line is:
app.Flag("provider", "The DNS provider where the DNS records will be created (required, options: aws, aws-sd, google, azure, azure-dns, azure-private-dns, cloudflare, rcodezero, digitalocean, hetzner, dnsimple, akamai, infoblox, dyn, designate, coredns, skydns, inmemory, ovh, pdns, oci, exoscale, linode, rfc2136, ns1, transip, vinyldns, rdns, scaleway, vultr, ultradns)").Required().PlaceHolder("provider").EnumVar(&cfg.Provider, "aws", "aws-sd", "google", "azure", "azure-dns", "hetzner", "azure-private-dns", "alibabacloud", "cloudflare", "rcodezero", "digitalocean", "dnsimple", "akamai", "infoblox", "dyn", "designate", "coredns", "skydns", "inmemory", "ovh", "pdns", "oci", "exoscale", "linode", "rfc2136", "ns1", "transip", "vinyldns", "rdns", "scaleway", "vultr", "ultradns")
Currently in the master branch the line is:
app.Flag("provider", "The DNS provider where the DNS records will be created (required, options: aws, aws-sd, godaddy, google, azure, azure-dns, azure-private-dns, cloudflare, rcodezero, digitalocean, hetzner, dnsimple, akamai, infoblox, dyn, designate, coredns, skydns, inmemory, ovh, pdns, oci, exoscale, linode, rfc2136, ns1, transip, vinyldns, rdns, scaleway, vultr, ultradns)").Required().PlaceHolder("provider").EnumVar(&cfg.Provider, "aws", "aws-sd", "google", "azure", "azure-dns", "hetzner", "azure-private-dns", "alibabacloud", "cloudflare", "rcodezero", "digitalocean", "dnsimple", "akamai", "infoblox", "dyn", "designate", "coredns", "skydns", "inmemory", "ovh", "pdns", "oci", "exoscale", "linode", "rfc2136", "ns1", "transip", "vinyldns", "rdns", "scaleway", "vultr", "ultradns", "godaddy")
The last accepted provider is now godaddy
.
So the issue seems to be fixed in the next release.
Just an educated guess. I don't know go code.
When next release will be available ?
There is godaddy example in repo with version 0.7.7 in it, but it's not available yet ? Why you are including it then ?
My pod fails to pull an image:
Failed to pull image "k8s.gcr.io/external-dns/external-dns:v0.7.7": rpc error: code = Unknown desc = Error response from daemon: manifest for k8s.gcr.io/external-dns/external-dns:v0.7.7 not found: manifest unknown: Failed to fetch "v0.7.7" from request "/v2/external-dns/external-dns/manifests/v0.7.7"
0.7.7 is not release yet, we will release it later this month. Please watch the github releases.
When will v0.7.7 (specifically GoDaddy?) i'm getting these error messages in my k8s pod...
kubectl logs external-dns-66894d95d4-5h4xf
time="2021-02-18T18:13:02Z" level=fatal msg="flag parsing error: unknown long flag '--godaddy-api-key'"
apiVersion: apps/v1
kind: Deployment
metadata:
name: external-dns
spec:
strategy:
type: Recreate
selector:
matchLabels:
app: external-dns
template:
metadata:
labels:
app: external-dns
spec:
serviceAccountName: external-dns
containers:
- name: external-dns
image: k8s.gcr.io/external-dns/external-dns:v0.7.6
args:
- --source=service # ingress is also possible
- --domain-filter=<taken out> # (optional) limit to only example.com domains; change to match the zone created above.
- --provider=godaddy
- --txt-prefix=external-dns. # In case of multiple k8s cluster
- --txt-owner-id=owner-id # In case of multiple k8s cluster
- --godaddy-api-key=<taken out>
- --godaddy-api-secret=<taken out>
---
Kind regards Andy