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
When started, Moco Operator goes through all StatefulSets in the cluster to find the ones it manages, i.e. which have an OwnerReference to a MySQLCluster CRD. However, for every StatefulSet it doesn't own, an error log line is output to the logs, stating that StatefulSet XXXX has no owner reference to MySQLCluster. This reconciliation is repeated on the timer, spamming the logs.
I'd like to argue that this is not an error and should be informative at best: it's perfectly normal to have StatefulSets in the cluster which are not Moco-operated, even if and especially if those StatefulSets are MySQL clusters created by another operator, e.g. when the intention is to migrate the database to Moco.
Environments
Version: 0.25.1
Expected behavior
No error messages are output, since there is no error state
The text was updated successfully, but these errors were encountered:
Describe the bug
When started, Moco Operator goes through all
StatefulSet
s in the cluster to find the ones it manages, i.e. which have anOwnerReference
to aMySQLCluster
CRD. However, for everyStatefulSet
it doesn't own, an error log line is output to the logs, stating thatStatefulSet XXXX has no owner reference to MySQLCluster
. This reconciliation is repeated on the timer, spamming the logs.I'd like to argue that this is not an error and should be informative at best: it's perfectly normal to have
StatefulSet
s in the cluster which are not Moco-operated, even if and especially if thoseStatefulSet
s are MySQL clusters created by another operator, e.g. when the intention is to migrate the database to Moco.Environments
Expected behavior
No error messages are output, since there is no error state
The text was updated successfully, but these errors were encountered: