-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
ship a better storage solution #1157
Conversation
note that this does unfortunately increase the node image size slightly, but having somewhat saner PVs is worth it. |
@@ -53,7 +55,7 @@ func (a *action) Execute(ctx *actions.ActionContext) error { | |||
node := controlPlanes[0] // kind expects at least one always | |||
|
|||
// add the default storage class | |||
if err := addDefaultStorageClass(node); err != nil { | |||
if err := addDefaultStorage(ctx.Logger, node); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we be able to opt-out and not install it as we did with the CNI?
or opt-in and keep the legacy by default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessary initially.
You can easily replace the storage class with your own and delete the deployment, unlike CNI.
Let me mark this PR WIP.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no point in opt-in. We ship hermetic images, the images etc. will already be there and just running the deployment is low cost.
And the legacy one is know to have major limitations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! 😃
@yashbhutwala: changing LGTM is restricted to collaborators In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, yashbhutwala 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 |
handled v1.11 node image builds by shipping the old manifest in that case (and not bundling the images) that's pretty low effort but will let us continue to best effort support v1.11 minimally without much code |
rebased to upstream and pushed the node image |
/lgtm |
This is great! Looking forward to the next release of Kind. Thank you! |
I did a LOT of testing with these. It should work great with the tweaks we've applied for kind :-) |
Is there a timeline / roadmap / due date for the next kind release? Very interested in this fix as i hit this with the Elasticsearch (elastic/helm-charts#429) and likely also the Prometheus chart (eclipse/packages#13 (comment)). |
#1250 working on it
nominally we use milestones, but that got a bit out of date over the
holidays.
…On Mon, Jan 13, 2020 at 6:32 AM André Bauer ***@***.***> wrote:
Is there a timeline / roadmap / due date for the next kind release?
Very interested in this fix as i hit this with the Elasticsearch (
elastic/helm-charts#429
<elastic/helm-charts#429>) and likely also the
Prometheus chart (eclipse/packages#13 (comment)
<eclipse/packages#13 (comment)>).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1157?email_source=notifications&email_token=AAHADK4B7IOYYTPJVW2YNSLQ5R3OBA5CNFSM4JZHNKT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIY5HWQ#issuecomment-573690842>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADK6UPAP75WSORPLTWTDQ5R3OBANCNFSM4JZHNKTQ>
.
|
the release is out!
On Mon, Jan 13, 2020 at 4:57 PM Benjamin Elder <[email protected]>
wrote:
… #1250 working on it
nominally we use milestones, but that got a bit out of date over the
holidays.
On Mon, Jan 13, 2020 at 6:32 AM André Bauer ***@***.***>
wrote:
> Is there a timeline / roadmap / due date for the next kind release?
>
> Very interested in this fix as i hit this with the Elasticsearch (
> elastic/helm-charts#429
> <elastic/helm-charts#429>) and likely also the
> Prometheus chart (eclipse/packages#13 (comment)
> <eclipse/packages#13 (comment)>).
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#1157?email_source=notifications&email_token=AAHADK4B7IOYYTPJVW2YNSLQ5R3OBA5CNFSM4JZHNKT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIY5HWQ#issuecomment-573690842>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAHADK6UPAP75WSORPLTWTDQ5R3OBANCNFSM4JZHNKTQ>
> .
>
|
Thanks a lot! :-) |
TODO:
I'll handle those later tonight. I just want to surface progress on this.
Fixes #1151 #118