0.2.4

This release fixes some bugs related to how Orchestrator does topology recovery. The list of changes is presented below:

• Keep last known state when orchestrator is down (#219), this will prevent master service to go down when Orchestrator is not available (#203);
• Cascade deletion of the cluster now will not delete all the resources (#221, #225);
• Update controller-runtime which implies using klog instead of glog (#227);
• Let the operator set the master writable (#222, #199) so now the operator does not set nodes in maintenance to prevent failover when the cluster is in read-only. Also, unwanted failovers, which can bring the cluster in co-master topology (#207) are prevented;
• Change what means for a cluster to be Ready, now the cluster is ready if all pods in StatefulSet are Running and replicating and the cluster has a master. (f85e674);
• Exclude init table from backup to allow bootstrap detection on slave (0dbcc88).