dcaputo-harmoni

Just FYI - have been running this image for 24 hours now and not a single error, which is a big change from dozens of errors (detailed in the github...

@egegunes @hors just made the change, let me know if that's what you are thinking. Appears to be working as intended on my side.

Looks like all the errors have come back on this last build. Since both the sync users and reconcile errors are occurring, it's probably not related to the retry methodology...

Here is some additional debugging info from the operator container (downloaded the latest release of websocat to it): ``` ./websocat "wss://10.0.64.1:443/api/v1/namespaces/core-mysql/pods/mysql-db-proxysql-0/exec?command=proxysql-admin&command=--syncusers&command=--add-query-rule&container=proxysql&stderr=true&stdout=true" --header="Authorization: Bearer $(cat /var/run/secrets/kubernetes.io/serviceaccount/token)" -k -E Syncing user accounts...

Further update - I've managed to get this working, see the last commit. In short, all of the exec commands could use error retrying, so I built the logic from...

I've added conforming retries to PodLogs and IsPodRunning, as those can occasionally encounter the same errors.

@egegunes No problem, just let me know when

I added in some proposed changes to make both concurrency and block size configurable for Azure storage endpoints, let me know if this is along the lines of what you...

Hi @hors just want to check in on this one, let me know if I can help get this resolved - it's an important feature for anyone running in an...

We are experiencing this same issue with a mysql8 backend for both the primary and visibility db's, would love to see it addressed as the web ui dashboards become cluttered...