Using bigint for MySQL/MariaDB id column

[bognerf]

Since installing a K3s cluster (2 control panes, 3 workers) with MariaDB 10.3 as a datastore backend, I can see the id column incrementing faster than expected. After several weeks I already hit 65 milllion with about 6000 rows.
Of course, 65 mio is not 2 billion, which would be the maximum for a signed int column at MariaDB, but I wonder if it would be safe to change the column type of id, create_revision and prev_revision to bigint unsigned.

Could you think of unintended side effects or is there anything I'm not aware of that would make this undesirable?

[brandond]

I've not seen anyone run into issues with this, but it should be possible to change it without it negatively affecting anything. Note that if you are concerned about this now, you should be able to run an ALTER TABLE on the database to change it; kine won't make any attempt to revert it.