This message was deleted.
# k3s
a
This message was deleted.
q
It might be related to this PR in kine: https://github.com/k3s-io/kine/pull/241 From what I can tell, this code now assumes that the
postgres
database exists and that the connecting user has access to use it and create databases? And it fails when that is not the case?
c
That is supposed to be a safe assumption, did you delete that database? https://www.postgresql.org/docs/9.1/creating-cluster.html
After initialization, a database cluster will contain a database named postgres, which is meant as a default database for use by utilities, users and third party applications. The database server itself does not require the postgres database to exist, but many external utility programs assume it exists.
q
No, but this is a managed database so it might be something the SaaS operator has done. Creating the database is supposed to be done via console/API, not directly from a db connection.
c
right but as the postgres docs indicate, that database can be reasonably expected to always exist as a baseline.
it’s not trying to create it, it’s trying to use it as a temporary database for the connection while it verifies that the selected k3s database exists
who is your database provider?
q
aiven.io .. they have a free tier 😄
c
interesting… would you mind opening an issue on the k3s repo?
q
I realised that if it's not actually expecting from the postgres database, other than its existence, I might get around it by simply creating it. Feels somewhat hacky, but I am allowed to create a database called postgres. Probably wastes some of the scarce diskspace the free tier gives me, but looks like I can allow upgrades again at the very least. I'll still create an issue, because I wouldn't be surprised if other SaaS providers might do similar things, but for now I have a workable workaround.
I struggled with the title, so feel free to give it a more concise title: 🙂 https://github.com/k3s-io/k3s/issues/9033
c
looks good!
q