Bump kine to v0.10.1

[brandond]

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.

[bruth]

@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 noEmbed URL param. For existing k3s deployments upgrading that are relying on an external NATS cluster, this param would need to be added.

[brandond]

@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 nats:// endpoint scheme, so that anyone using the legacy jetstream:// scheme will get the old behavior of connecting to the given address. This would avoid breaking users when we add the embedded server support.

[bruth]

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?

[brandond]

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 ;)

[bruth]

PR for Kine: k3s-io/kine#184

[bguzman-3pillar]

Validated kine v0.10.1 version using go.mod on 1.27 branch

Look for line 108