[Request]: external-dns refresh exoscale provider

[ivankatliarchuk]

Your request

Hello.

We are maitainers of external-dns. Is anyone have any interest to refresh exoscale provider https://github.com/kubernetes-sigs/external-dns/blob/master/provider/exoscale/exoscale.go?

We have 3 options

• we are going to remove it in one of the next releases, as it's abandoned
• we neede someone with access to exoscale to refresh provider (and test it working against real infrastructure)
• or create a webhook https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/webhook-provider.md

[pierre-emmanuelJ]

Hello, thanks for your issue.

The current implementation should work since it's based on the Exoscale API v2, and nothing changed on the DNS API side.
We can first provide a test result showing the provider still working against real Exoscale infrastructure.

Not urgent, but in a second phase we can on our side refresh this provider with the lastest version of egoscale V3

Should we exchange via email or Kubernetes SIGs Slack?

EDIT:

And I think we are using this project internally, so we really still need to be part of the releases.

[ivankatliarchuk]

That's fine. It would be nice to refresh when you have capacity. No need to exchnage of msg, open a PR and will pick it up ;-)

[natalie-o-perret]

Update

• I've opened a PR on the external-dns side to refresh the Exoscale provider while fixing one of our customers apex record issues and test it against actual infrastructure: refactor(exoscale): migrate provider to egoscale v3 and apex DNS record handling kubernetes-sigs/external-dns#6371
• The webhook approach is on our radar as a potential follow-up, will revisit once the refresh lands.

[natalie-o-perret]

@ivankatliarchuk, I think we can consider this issue done, wdyt?

[pierre-emmanuelJ]

thanks a lot @natalie-o-perret for the refresh :)