feat: add support for PTR, MX and DS record types

[castorw]

What does it do ?

This PR allows use of the following record types:

• PTR - Reverse IP mapping to forward records,
• MX - Mail server record for domain,
• DS - Delegations signer (used to establish a chain of trust for DNSSEC)

Motivation

While setting up external-dns as provisioner for reverse zones I noticed that the controller gets in a conflict loop while trying to create records which already exist. It creates records and then in the next loop attempts to create these again. This is caused by a simple omission of allowed record types in the recordfilter.go file. This will allow users to manage wider range of records.

More

• Yes, this PR title follows Conventional Commits
• Yes, I added unit tests
• Yes, I updated end user documentation accordingly
  • not much to update as the docs basically states that this should work

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign raffo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: castorw / name: Lubomir Kaplan (488cf8c, c84dba0)

[k8s-ci-robot]

Welcome @castorw!

It looks like this is your first PR to kubernetes-sigs/external-dns 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/external-dns has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @castorw. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[ivankatliarchuk]

Ups

[castorw]

Yeah....

[castorw]

@ivankatliarchuk Can we please remove this PR? I will open another one. The source branch is fixed already. But the very unwanted file is still visible in PR.

[ivankatliarchuk]

I do not have any maintainer or developer access to repo. I could only review/approve with the help of comment labels.

Kubernetes project is quite strict with access rights.

[castorw]

Okay never mind, my bad. Here's a new one #6337.
Gonna reissue a CA now 🫤
Thanks.