-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Bump kine to v0.10.1 #7410
Comments
@brandond Curious to know what the plan would be on when embedded NATS will be included? It is also worth noting that when it does become enabled, it will result it defaulting to the embedded server unless the endpoint URL explicitly has the |
@bruth Not sure, but that is a great callout that didn't occur to me. I wonder if perhaps we should make an additional change to kine so that the embedded server is only enabled by default with the |
I think that is a good idea. I will open a PR to revert to that behavior. That would also make it more comfortable to include embedded NATS to k3s to not change behavior.. especially if its only a 1MB increase? |
yeah absolutely. I am working on moving containerd back into the main binary which will save us 11MB, so that'll give us more room for nats ;) |
PR for Kine: k3s-io/kine#184 |
Kine v0.10.1 contains a number of bugfixes and enhancementes, see k3s-io/kine@v0.9.9...v0.10.1
We should update k3s to this version.
Note: at this time I am not planning on enabling the embedded nats support, which adds ~1mb to the shipping k3s binary size.
The text was updated successfully, but these errors were encountered: