1. don’t use --cluster-init and --cluster-reset at the same time
2. you’re not on the latest 1.22 patch; I believe this bug has been fixed - but in the mean time, i suspect that you’re using --secrets-encrypt when running k3s? if so you also need to pass that when running the --cluster-reset command
3. get to the latest 1.22 release if at all possible; preferably up to 1.23 and then 1.24 as both 1.22 and 1.23 are end of life.