https://rancher.com/ logo
Join Slack
Powered by
Hope it's alright to ask a question about kine her...
# k3s
p
Hope it's alright to ask a question about kine here 😁 - question being, are there any tests for kine specifically which databases are supported?
c
yes?
there is a test runner script for each database engine, inside that script you will find what versions it covers
p
Thank you, I missed that directory when I was looking for tests. I tried to update our k0s the other day and hit a weird bug. And the only thing we can't get a handle on is kine version versus postgres version. I thought that maybe postgres 14 was not supported anymore. But it looks like part of that test runner. So I guess it should work?
c
it should yes. you’re not using pgbouncer or anything else weird are you?
p
No, single postgres database
c
should work fine. you can see the results of the tests in the CI output
what specifically are you seeing?
idk what version of kine k0s is using. you might reach out to them.
p
I already did, one sec
Basically my api server dies hard
Crash loop
I performed the same upgrade on another cluster where we use kine/etcd and it worked. This cluster is different that we use kine/postgres.
c
maybe you should try k3s :)
p
GitHub.com/k0sproject/k0s/issues/8246 has some logs. A lot of it is pointless noise though.
E.g. the service-ip related seems a false positive (or upstream bug) where an existing value is not logged so the log line looks like a problem
c
lol they are on an ANCIENT version of kine that is missing a ton of features
p
Yes, the bumped it with 1.36
c
have you tried updating to 1.36?
p
Yeah, that's what the ticket is about
I might try their latest, they included some fixes
Anything I should read up on since this is a hefty jump?
c
the issues says 
Version v1.35.7+k0s.0
so I assumed that was still what you were on
p
I rolled back to it, this happened when I tried to go from 1.35 to 1.36
Currently I am on that 1.35.x still
c
I don’t know if k0s lets you do this, but you might start the kine container with KINE_SCHEMA_MIGRATION=2 and see if that changes anything
💡 1
Or manually run a standalone kine against the DB with that env var set, you only need to do it once
p
I'll have to go check how they embed kine
c
p
Maybe this is taking a bit
And crashes before it’s done
I guess I could run these
I am a bit slow 😂
Thanks for taking the time btw
c
schema migrations aren’t enabled by default
p
Roger
n
This discussion is a reminder I need to check our suite of DB and remove/update EOL versions
p
The docs in k3s also suggest only psql15 is tested
I am not sure where this verification comes from
n
On the k3s side, QA regularly validates against newer DB, but I forget to update the docs.
They track that via issue. github.com/k3s-io/k3s/issues/14101
p
What's the policy of no longer testing older versions?
n
Generally just if any DB version is EOL from that projects perspective, we don't test it
I would need to dig into the QA side (not publicly visible) and see what their currently nightly suite of DB looks like
But for kine, its really just the test list that Brad pointed to above, with me periodically "shifting" the window the DB versions we test
Open in Slack
PreviousNext
Powered by