-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
upgrading kube-builder #650
Comments
it's not particularly intended that people update their scaffolding (the scaffolding is one-time setup, or is supposed to be), but when we do the scaffolding v2 release, we'll be providing migration instructions if you want to move over to the simplified format. Does that answer your question? |
I asked this question because the scaffolding did in fact change over time and I had an issue that was fixed and I had to dig through issues and commit diffs to find how to manually apply the changes. Are changes to the scaffold such rare? (I mean, you guys know better then me, I'm just sharing from my experience) |
Scaffolding changes should be relatively rare, and it's not intended that we change scaffolding without reving the version if it's a breaking change. I'm curious as to which change you had to apply manually. |
This is one issue that I remember of: #595 |
ah, yeah... we don't really have a good story for dealing with that right now, unfortunately. I'm certainly open to suggestions though. |
/kind feature |
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. |
We've got a section for migration in the docs now. I don't foresee scaffolding changes being automatic, so closing for now. |
Is there an upgrade story for kube-builder? the gitbook talks about updating dependencies, but much of what kube-builder is is what's being scaffolded.
I don't know threre's a good colution for this but at least document changes so that people can manually apply.
The text was updated successfully, but these errors were encountered: