search

kubernetes-sigs / external-dns

Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
Apache License 2.0
7.58k stars 2.54k forks source link

Gandi provider is not found in 0.8.0 #2179

Closed gAmUssA closed 3 years ago

gAmUssA commented 3 years ago

What happened: following https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gandi.md two things 

time="2021-07-16T05:05:21Z" level=fatal msg="flag parsing error: enum value must be one of aws,aws-sd,google,azure,azure-dns,hetzner,azure-private-dns,alibabacloud,cloudflare,rcodezero,digitalocean,dnsimple,akamai,infoblox,dyn,designate,coredns,sky │
│ dns,inmemory,ovh,pdns,oci,exoscale,linode,rfc2136,ns1,transip,vinyldns,rdns,scaleway,vultr,ultradns,godaddy,bluecat, got 'gandi'"

What you expected to happen:

external-dns would work with gandi

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

kubectl apply -f file from example https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gandi.md

Anything else we need to know?:

Environment:

cc @packi

inisitijitty commented 3 years ago

According to this reply gandi support will be present in >=v0.9.0

seanmalloy commented 3 years ago

According to this reply gandi support will be present in >=v0.9.0

Yes, that is correct the Gandi provider code is merged to the master branch, but it did not make the cut for the v0.8.0 release. The Gandi provider should be available in the next release.

Thanks.

/close

k8s-ci-robot commented 3 years ago

@seanmalloy: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/2179#issuecomment-881507421): >> According to this [reply](https://github.com/kubernetes-sigs/external-dns/pull/2037#pullrequestreview-690293883) gandi support will be present in >=v0.9.0 > >Yes, that is correct the Gandi provider code is merged to the master branch, but it did not make the cut for the v0.8.0 release. The Gandi provider should be available in the next release. > >Thanks. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
gAmUssA commented 3 years ago

@seanmalloy could you point me to how to build a custom image from master?

seanmalloy commented 3 years ago

@seanmalloy could you point me to how to build a custom image from master?

The simplest option is probably to pull the container image from the staging registry. Every time a commit is push to the master branch a container image is built and pushed to this registry.

https://console.cloud.google.com/gcr/images/k8s-staging-external-dns/GLOBAL/external-dns?gcrImageListsize=30

Important note these images are not officially released images. Images in the staging registry may get deleted at some point in the future. Use in production at your own risk.