> Note: AWS has supported this for many years: https://aws.amazon.com/blogs/aws/new-hibernate-your-ec2-inst https://aws.amazon.com/blogs/aws/new-hibernate-your

> Note: AWS has supported this for many years: https://aws.amazon.com/blogs/aws/new-hibernate-your-ec2-inst https://aws.amazon.com/blogs/aws/new-hibernate-your-ec2-inst... We have been using GCP hibernation since 2018 too, but it was alpha back then. The AWS version also had some limitations (it only supposed Amazon Linux at the time) - current prerequisites here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hibernating-prerequisites.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hibernat... We have hundreds of developer K8s clusters that get used during a normal workday and get shutdown later. Because there are many services (each with their own readiness criteria), a cold boot takes a long time until all services stabilize (worst case I've seen was over 30 minutes). With hibernation they can resume where they started off within a couple of minutes. During development it's often the case that one may be doing experiments and changing the current state, so preserving everything is a plus. If, as it was often the case when it was alpha, hibernation failed, then the normal startup procedure would take place. We don't use it in production but I don't think it's inconceivable that there are other use-cases where preserving state could shave time in getting resources ready.