You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I try to manage mariadb-operator resources with an internal helm app and we're facing a technical issue with backup CRD.
Backup CRD is a cronjob and the app health is shown as progressing until cronjob is executed for the first time.
Healthy app:
NAMESPACE NAME COMPLETE STATUS MARIADB AGE <namespace> backup-scheduled True Success <cluster> 22h
Progressing app:
NAMESPACE NAME COMPLETE STATUS MARIADB AGE <namespace> backup-scheduled False Scheduled <cluster> 6m17s
For the progressing app, the cronjob last schedule is none.
For now, i use a lua script to manage mariadb-operator backup object and set status when reason is 'CronJobScheduled'.
Have you ever face a similar issue (with mariadb-operator or other) and how did you solve it ?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions