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.

Sign up for GitHub

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

Jump to bottom

Action Required for upgrading from kubebuilder <=v1.0.7 to >= v1.0.8 #557

Closed
mengqiy opened this issue Jan 8, 2019 · 3 comments
Closed

Action Required for upgrading from kubebuilder <=v1.0.7 to >= v1.0.8 #557

mengqiy opened this issue Jan 8, 2019 · 3 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@mengqiy
Copy link
Member

mengqiy commented Jan 8, 2019

TL;DR: If you don't have a project generated by kubebuilder v1.0.7 or earlier, you can stop reading.

If you have a project generated by kubebuilder v1.0.7 or earlier and you want to upgrade you kubebuilder to v1.0.8 or later, you need to do the following:

  1. Upgrade controller-runtime to version v0.1.9 or later and controller-tools to v0.1.8 or later.
dep ensure -update sigs.k8s.io/controller-runtime sigs.k8s.io/controller-tools
  1. Upgrade kubebuilder to v1.0.8 or later.
@mengqiy
Copy link
Member Author

mengqiy commented Jan 8, 2019 •
edited
Loading

This is not an actual issue, but serves as kinda release document.

@mengqiy mengqiy changed the title Action Required for older kubebuilder (<=v1.0.7) projects Action Required for upgrading from kubebuilder <=v1.0.7 to >= v1.0.8 Jan 8, 2019
mengqiy pushed a commit to mengqiy/kubebuilder that referenced this issue Jan 8, 2019
🏃 use 1.12.3 k8s binaries. [Action Required for upgrading from kubebu…
524286f 
…ilder <=v1.0.7 to >= v1.0.8] please read kubernetes-sigs#557
@mengqiy mengqiy mentioned this issue Jan 8, 2019
Merged
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 29, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DirectXMan12 @mengqiy @k8s-ci-robot @fejta-bot