Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provider: Add support for OVH DNS #809

Closed
thudry opened this issue Dec 7, 2018 · 13 comments
Closed

Provider: Add support for OVH DNS #809

thudry opened this issue Dec 7, 2018 · 13 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. new-provider

Comments

@thudry
Copy link

thudry commented Dec 7, 2018

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

@njuettner njuettner added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Dec 7, 2018
@njuettner
Copy link
Member

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

@Zwordi
Copy link

Zwordi commented Apr 5, 2019

Hi,

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

@elavrom
Copy link

elavrom commented May 9, 2019

Hey,

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

@njuettner
Copy link
Member

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

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2019
@yctn
Copy link

yctn commented Aug 20, 2019

Anyone working on this? would be very nice to have

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 19, 2019
@Zwordi
Copy link

Zwordi commented Oct 8, 2019

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... 🙏

@fejta-bot
Copy link

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

@k8s-ci-robot
Copy link
Contributor

@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.

@zedtux
Copy link

zedtux commented Dec 10, 2019

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

@Zwordi
Copy link

Zwordi commented Dec 10, 2019

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’re 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’m not mapping it on the host-network. I will updated my forum post as soon as possible.

@zedtux
Copy link

zedtux commented Dec 11, 2019

Thank you for sharing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. new-provider
Projects
None yet
Development

No branches or pull requests

8 participants