and its fireing these crazy statements

| SELECT *
		FROM (
			SELECT (
		SELECT MAX(rkv.id) AS id
		FROM kine AS rkv), (
		SELECT MAX(crkv.prev_revision) AS prev_revision
		FROM kine AS crkv
		WHERE crkv.name = 'compact_rev_key'), kv.id AS theid, kv.name, kv.created, kv.deleted, kv.create_revision, kv.prev_revision, kv.lease, kv.value, kv.old_value
			FROM kine AS kv
			JOIN (
				SELECT MAX(mkv.id) AS id
				FROM kine AS mkv
				WHERE
					mkv.name LIKE '/registry/leases/kube-system/k3s-cloud-controller-manager'
					
				GROUP BY mkv.name) AS maxkv
				ON maxkv.id = kv.id
			WHERE
				kv.deleted = 0 OR
				0
		) AS lkv
		ORDER BY lkv.theid ASC

that’s not particularly crazy, thats one of our standard queries

@creamy-pencil-82913 Iam worried about the produced load on our galera cluster system. Is K3s to be known as supported running with percona galera?

No, we've not tested it on that, and I suspect you're getting a bunch of skip records created as described in that issue.