Brad Davidson
Brad Davidson
The way we use the Helm controller to deploy core cluster infrastructure whose complete configuration is managed by the chart, it's usually best for us as distribution maintainers to default...
> Retrying upgrade of longhorn > Error: UPGRADE FAILED: post-upgrade hooks failed: timed out waiting for the condition OK, so the `helm upgrade` operation is timing out. It's taking longer...
That might be hard, since kine expects a SQL compatible storage engine. Seems like if you want an ephemeral dataatore you could get the same result out of sqlite with...
What specifically are you trying to achieve?
fwiw, I tried using sqlite in memory mode and it's pretty flakey, due to changes in table locking semantics. ``` docker run --rm -it --privileged --name k3s-server-1 rancher/k3s server --datastore-endpoint...
You could just use kine but store the SQLite database in a temporary directory that's not persistent?
You're welcome to try it and see if it works for you. It didn't work very well for a whole Kubernetes cluster using the example command I gave.
yep. Some of the requirements to use the sqlite in-memory store are described here: https://www.sqlite.org/inmemorydb.html - I don't remember specifically what I ran into with locking, but it should be...
Seems to be the same issue described here: https://github.com/mattn/go-sqlite3/issues/50#issuecomment-87811607
No, I don't believe you should have to create the stream. Do you perhaps need to specify the port in addition to the container hostname in the `nats://` URI? What...