-
Notifications
You must be signed in to change notification settings - Fork 47
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
Upgrade coredns to kubebuilder 2 #24
Comments
Now that kubernetes-sigs/kubebuilder#943 is landed, I built it from master (no new release yet - kubernetes-sigs/kubebuilder#1001) using
(because tests failed for some reason). After that I created a new directory and ran:
Then I followed the instructions in the The resulting diffstat looks like this:
I'm spelling all of this out, so we can document it in #11 and as part of this issue. |
@johnsonj recommended I pull kubernetes-sigs/kubebuilder#1059 and try again. The outcome is fairly similar:
The full diff can be seen here: https://gist.github.com/dholbach/d55b93f8055ca6eb8df5e7895bb5e94c |
/assign |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
@rajansandeep are you working on it? |
@vaibhavk, I am working on this :) |
Kubebuilder 2.0 is approaching and results in significant change in directory structure.
We should migrate the coredns operator to this (either re-create and retain the custom bits or manually diff?) once 2.0 is released.
Here's an example PR
The text was updated successfully, but these errors were encountered: