This document describes the possible design and implementation of a method to hibernate IPI (ocp) clusters.
-
IPI clusters do not have a hibernation support yet
-
An active IPI cluster uses multiple cloud resources in backend
-
Cumulative cost of these cloud resource turns to be the cloud cost to host the IPI cluster
-
Top cloud resource to contribute to the cluster cost is:
- EC2 instances
-
Find all the running EC2 instances for a given IPI cluster
-
The corresponding EC2 instances should be stopped (NOT terminated)
- This would save the cost of EC2 instances for the duration of hibernation
-
This design is implemented here:
-
Find all the stopped EC2 instances for a given IPI cluster
-
The corresponding EC2 instances should be started
- As soon as the instances are up and running, the cluster will be back to the active running state
-
This design is implemented here: