UI backup scheduling inserting trailing zero in cron job minutes config
Summary
When updating a backup schedule in the UI, an extra zero is added to the minutes component of the cron string causing it to be invalid
Current Behaviour
Extra 0 added to minutes component, so trying to schedule for daily 15:59 produces "590 15 * * *"
Steps to reproduce
- Update minutes in backup config schedule to >=10,<=59
kubectl get -o yaml <cluster-name>
- Observe the incorrect config
Expected Behaviour
Schedule is added as entered
Possible Solution
The field is not being properly synchronized and the default value is being appended to the entered value
Environment
- StackGres version: 1.3.0
- Kubernetes version: 1.24.4
- Cloud provider or hardware configuration: