Hi, I'm using k3s and have mysql as backend server and have now run into a issue where I have reached the maximum number for the

id

field. I receive the error

Duplicate entry '2147483647' for key 'PRIMARY'

from the database. Any hints on how to fix this?

I have honestly never seen that happen. Unless there is something wrong with the database, K3s should be able to run for years before you get anywhere near hitting sqlite’s maximum integer value for the ID field. You could try doing

ALTER TABLE kine CHANGE id id BIGINT NOT NULL AUTO_INCREMENT

but this hasn’t been tested, obviously should not be done while the database is in use, and may take a while to run. Would you mind opening an issue in the K3s repo describing your environment? I’d like to understand what might have caused this.

This cluster have been up and running for 18 months and have ~200 nodes. I was thinking of changing id to BIGINT but realized that this might break stuff. I'll create a issue in the k3s repo

Hmm. 200 nodes is definitely on the larger side for a k3s cluster. More important is going to be the churn rate on cluster resources though, which will depend on what you have deployed to it and how much it actually stores in kubernetes vs just being orchestrated by it. What version of K3s are you currently on?

We are still on v1.22.12+k3s1