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

Create SafeDNS provider #2359

Merged
merged 8 commits into from
Jan 5, 2022
Merged

Create SafeDNS provider #2359

merged 8 commits into from
Jan 5, 2022

Conversation

rjhenry
Copy link
Contributor

@rjhenry rjhenry commented Oct 8, 2021

Description
Create a provider for UKFast's SafeDNS.

Checklist

  • Unit tests updated
  • End user documentation updated

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


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. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Oct 8, 2021
@k8s-ci-robot
Copy link
Contributor

Welcome @rjhenry!

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 k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Oct 8, 2021
@k8s-ci-robot
Copy link
Contributor

@rjhenry: What did the ocean say to the beach? Thanks for all the sediment.

In response to this:

/joke
/lint
/check-cla

(Multiple commands to visually get a response)

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.

@rjhenry
Copy link
Contributor Author

rjhenry commented Oct 8, 2021

/check-cla
/joke

@k8s-ci-robot
Copy link
Contributor

@rjhenry: What did one snowman say to the other snow man? Do you smell carrot?

In response to this:

/check-cla
/joke

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.

@rjhenry
Copy link
Contributor Author

rjhenry commented Oct 8, 2021

/check-cla

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Oct 8, 2021
@rjhenry
Copy link
Contributor Author

rjhenry commented Oct 8, 2021

/assign raffo

@rjhenry
Copy link
Contributor Author

rjhenry commented Oct 8, 2021

/assign reviewers

@k8s-ci-robot
Copy link
Contributor

@rjhenry: GitHub didn't allow me to assign the following users: reviewers.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign reviewers

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.

@rjhenry
Copy link
Contributor Author

rjhenry commented Oct 8, 2021

/assign njuettner raffo seanmalloy

@rjhenry
Copy link
Contributor Author

rjhenry commented Oct 8, 2021

Apologies for the mess of comments on the PR - getting used to the format! Should be in the correct state for Phase 1 - human review.


This tutorial describes how to setup ExternalDNS for usage within a Kubernetes cluster using SafeDNS

Make sure to use **>=FIXME** version of ExternalDNS for this tutorial.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll fix this once I've got a a point of "this PR is reviewed to a technical level", so it can be relatively confident as to which version should be referred to.

The same goes for the two container image tags in examples below.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rjhenry can ypu replace the fixme with 0.11.0? It will be unreleased when we merge this, but it is the next tag for release. Once you change that we're good to merge this one.

@rjhenry
Copy link
Contributor Author

rjhenry commented Nov 3, 2021

@Raffo @seanmalloy @njuettner Is there any idea on when this PR may be able to be looked at? I'm keen to get this in place so I can switch back to the upstream images for ExternalDNS.

@Raffo
Copy link
Contributor

Raffo commented Nov 3, 2021

@rjhenry we're incredibly resource constrained this month, so that might take a bit unfortunately.

@rjhenry
Copy link
Contributor Author

rjhenry commented Dec 7, 2021

@Raffo @seanmalloy @njuettner Now that another month has passed, is there any more likelyhood of being able to review this PR, or are you still incredibly resource-constrained?

@rjhenry
Copy link
Contributor Author

rjhenry commented Dec 7, 2021

(Note: Rebased from v0.10.0 to v0.10.1, and improved lint quality)

@Raffo
Copy link
Contributor

Raffo commented Dec 17, 2021

@rjhenry yes, we’ll take a look in a bit.

Copy link
Contributor

@Raffo Raffo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rjhenry I added a few comments, changes look good overall. I’d be happy to approve this PR once the comments are addressed. Can you please also make sure to add yourself as a maintainer of this code in the README section? We ask for people contributing new provider to provide as well some level of support for the code they will commit.

docs/tutorials/UKFast_SafeDNS.md Outdated Show resolved Hide resolved
docs/tutorials/UKFast_SafeDNS.md Outdated Show resolved Hide resolved
docs/tutorials/UKFast_SafeDNS.md Outdated Show resolved Hide resolved
provider/safedns/safedns.go Outdated Show resolved Hide resolved
provider/safedns/safedns.go Outdated Show resolved Hide resolved
Comment on lines 187 to 191
// TODO: Find a more effient way of doing this.
// Currently iterates over each zoneRecord in ZoneRecords for each Endpoint in UpdateNew; the same will go for
// Delete. As it's double-iteration, that's O(n^2), which isn't great.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be concerned about this? Is it something we are okay to merge like it is and then reconsider in the future?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I haven't noticed any issues running this code in production for an account with many hundred of zones, each with many hundreds of records. On that basis alone, I'd say that it's okay to merge now and reconsider in future.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok sounds good. I would prefer if we leave the TODO then if we do not need any change for now, so that we can search TODOs for real things that are left to do in the codebase.

}
}
for _, endpoint := range changes.Delete {
// TODO: Find a more effient way of doing this.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replied above.

@rjhenry
Copy link
Contributor Author

rjhenry commented Dec 17, 2021

Can you please also make sure to add yourself as a maintainer of this code in the README section?

I have added my organisation as a maintainer, and not myself as an individual. The organisation has a use for this, but myself as an individual does not, so it makes more sense - in my mind - for the organisation to be deemed the maintainer of this plugin.
If you'd prefer an individual, I can change this for now, though note that I'd likely avoid being a maintainer of code I don't use if I were to leave @assureddt.

@Raffo Raffo closed this Dec 20, 2021
@Raffo Raffo reopened this Dec 20, 2021
Copy link
Contributor

@Raffo Raffo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rjhenry if you drop the TODOs, I’m ok to approve this PR.

@rjhenry
Copy link
Contributor Author

rjhenry commented Dec 20, 2021

I've dropped the TODOs, but kept the comment about the complexity; it's likely to be a good place to look if any performance issues are reported. I've also rebased to be based on v0.10.2 rather than v0.10.1.

Many thanks for working with me on this @Raffo!

@Raffo
Copy link
Contributor

Raffo commented Jan 5, 2022

@rjhenry I have a comment to solve in https://github.com/kubernetes-sigs/external-dns/pull/2359/files#r778642557 then we can merge this PR.

EDIT: there is an issue with the linter, please fix that as well (see CI).

Rick Henry and others added 8 commits January 5, 2022 09:22
Keeping the comments in some degree is valuable, as it clarifies the
time complexity of the operations done; in the event of a performance
issue, this would likely be somewhere to look. However, remove the
`TODO` string directly, as it is not an urgent look-at-me-now.
@rjhenry
Copy link
Contributor Author

rjhenry commented Jan 5, 2022

@Raffo I've removed the FIXME (and it's corresponding one in the image name, in the documentation) and fixed the lint issue; is there anything else you need from me here?

Copy link
Contributor

@Raffo Raffo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 5, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Raffo, rjhenry

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2022
@k8s-ci-robot k8s-ci-robot merged commit c8ef365 into kubernetes-sigs:master Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants