Proposal moving ExternalDNS into Kubernetes organization

[njuettner]

A proposal to move ExternalDNS out of kubernetes-incubator and move it into the Kubernetes organization.

[k8s-ci-robot]

Welcome @njuettner!

It looks like this is your first PR to kubernetes/enhancements 🎉. 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/enhancements 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 @njuettner. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[njuettner]

/assign @dcbw

[njuettner]

Any feedback for us? It would be nice if someone could look at it. Highly appreciate your feedback 🙂 @thockin @caseydavenport @dcbw

[mrbobbytables]

Hey there @njuettner Just an FYI - you don't actually need to make a KEP to migrate a repo across kubernetes orgs 👍

The Kubernetes incubator org has been deprecated and there's an outstanding issue about migrating the various repos to the kubernetes-sigs org.

To initiate it, it'd be best to send a message to the owning sig mailing list to get broader buy-in regarding the move. After that, it's filing a New Repo / Migrate Repo request in the kubernetes/org repo.

Hope that helps!

[njuettner]

@mrbobbytables thank you for your reply. We didn't know about that and thought it would be a good idea to write a KEP.

I was writing to sig-network mailing group before and they were so nice to answer my question to create a PR first so that it can be approved.

This was brought up a couple months ago as I recall. The next step was a KEP - I see there is one in the external DNS project. The intent would be to put one in k/enhancements where it would be seen by others and could be approved by the SIG.

Can you send a PR with that KEP to k/enhancements - specifically here: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network

Then we can comment and hopefully approve once it's to everyone's satisfaction.

See: https://groups.google.com/forum/#!topic/kubernetes-sig-network/KOpzXgWcCMA

So I'm a bit lost now what I need to do, if it's only creating a new issue to migrate the project I'm happy to do that.

[mrbobbytables]

So I'm a bit lost now what I need to do, if it's only creating a new issue to migrate the project I'm happy to do that.

Hm, it may be worth getting it on the agenda for an upcoming sig-network meeting to get everything sorted out.

[Raffo]

@mrbobbytables @njuettner just for completeness, this is where I was asked to write a KEP: https://groups.google.com/d/msg/kubernetes-sig-network/fvpDC_nxtEM/lmn4ksWaBgAJ

After some work, that got merged in the ExternalDNS repo to eventually create this enhancement request.

[bowei]

This makes sense -- you should definitely advertise this in sig-network call if possible to get the ACKs needed to move the project.

[bowei]

/assign bowei@

[njuettner]

/assign bowei

[bowei]

/lgtm

@thockin

[bowei]

/ok-to-test

[bowei]

/lgtm

[bowei]

@thockin this is already done, we should /approve and merge

[bowei]

ping

@thockin @caseydavenport this is already done -- we should merge this for historical purposes.

[thockin]

Thanks!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, njuettner, thockin

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:

• keps/sig-network/OWNERS [thockin]

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