This message was deleted.
# k3sa
adamant-kite-43734
10/17/2022, 9:07 PMThis message was deleted.
c
creamy-pencil-82913
10/17/2022, 9:17 PMThis file is generated on startup, there’s no point in backing it up/etc/rancher/k3s/k3s.yaml
creamy-pencil-82913
10/17/2022, 9:18 PMYou should also back up
/var/lib/rancher/k3s/server/tokena
ancient-raincoat-46356
10/17/2022, 9:21 PMAh yes. I mixed those two up. I knew there was something else I needed along with the snapshots... The token.
ancient-raincoat-46356
10/17/2022, 9:22 PMHow come the docs don't mention some of the other possible files? I'm including one because my master nodes need an env var to route through a proxy, but when I researched to figure that out, there were 3 different places I could have put those. The Backup/Restore documentation mentions none of that.
c
creamy-pencil-82913
10/17/2022, 9:26 PMIts assumed that if you configure k3s, you know what/where you configured and would also restore that.
creamy-pencil-82913
10/17/2022, 9:28 PMIf you’re managing the configuration of your nodes, all you should need to back up are things generated by k3s itself. Everything else should be handled by your configuration management system.
a
ancient-raincoat-46356
10/17/2022, 9:42 PMPoint well made. Thank you!