When a new cluster is installed with hibernateAfter set and spec.powerState is not Hibernating, it does not yet have a Status.powerState, and the current logic of the hibernation controller does not set the Status.powerState until hibernation is triggered. Instead, the cluster is requeued until hibernation is hit.
 
Additionally, in cases where the hibernatingCondition.Status and readyCondition.Status are corev1.ConditionUnknown, the hibernation controller assumes that the cluster is newly initialized. This does not account for cases of adoption or disaster recovery. In these cases, the controller should check the running status of the cluster and update Status fields accordingly.