External-dns: Provider: Add support for OVH DNS

Created on 7 Dec 2018  路  13Comments  路  Source: kubernetes-sigs/external-dns

OVH offer an api to manage DNS.
It would be great if this provider could be integrated

Resources:
API reference https://eu.api.ovh.com
Package to interact with the API: https://github.com/ovh/go-ovh

good first issue help wanted lifecyclrotten new-provider

Most helpful comment

Anyone working on this? would be very nice to have

All 13 comments

We're always open for PR's 馃憤. I added some labels, in case of anyone wants to help here 馃槃.

Hi,

I'm willing to help !
Have a nice week-end to you all.

Hey,

Are you guys working on this ? I could really use it at work !

This should come from the community. We're not using OVH

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Anyone working on this? would be very nice to have

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Guys, I managed to have something working using Traefik as Ingress with OVH as a provider. But still it would be nice to have external-dns project support more and more provider.

May the Dev gods heart my pray... 馃檹

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Zwordi would you mind to share how you did it?

Hi @zedtux , you can have a look here still working on it regarding security headers etc, but i have currently no issue about the certificats side. Just be carefull about how you鈥檙e doing the port mapping from the nodes side host network. The current example on my link will lead to have no client-ip at all as i鈥檓 not mapping it on the host-network. I will updated my forum post as soon as possible.

Thank you for sharing.

Was this page helpful?
0 / 5 - 0 ratings