This message was deleted.

I’m not sure of an ‘official’ answer, but in my testing I often just do

shutdown -t now

when shutting down a node running harvester. My VMs are typically shut down gracefully and I don’t have problems starting the node back up (this is for a single node harvester setup)

thank you much. I'm looking for the "perfect" "all-in-one" command or all the steps needed to script it, if it doesn't exist. There's definitely some "new to me" technology bundled in harvester and I'd prefer to not miss anything. The only thing I am seeing in my searches is that I am not the only one looking for such a thing. So do you do anything for the kubernetes "parts" prior? I found this, but not certain if its all relevant or already scripted into a proccess/command I am unaware of. https://www.suse.com/support/kb/doc/?id=000020031

I believe that the harvester cluster is able to handle graceful shutdown of all the resources. At least in all my testing, I am able to shut down with that command and bring it back up the next day with no issues. Since you are also using 1 node in your testing environment, it should work the same. But I can check with my team if you want a more reliable answer 🙂

I'd be inclined to think harvester handles shutting down the resources as well, but was just trying to make sure I'm not assuming one thing, but reality is a different outcome. I'm going to be foolishly pushing this to a "production" type scenario quickly. As production-ish as you can get 1 node anyway. It's still home use at this point and I know I'll probably create myself some pain points in doing so, but I just think of myself as a guinea pig. Thanks again.