Viacheslav Sarzhan
Viacheslav Sarzhan
@cars-matt-b, please provide an example of your CR, and I will try to help you.
@cars-matt-b any update?
I'm going to close this issue, as there hasn't been any activity for several months. If you're still experiencing the problem, please feel free to open a new issue with...
@abh Thank you for the testing. We will check it today.
> Here's the operator log. I had reset a cluster entirely because group replication had failed, and it looks like the operator never got to update the status with the...
> ``` > 2025-09-26T01:20:01.900862Z 36 [Note] [MY-010926] [Server] Access denied for user 'mysql_innodb_cluster_42132052'@'10.42.4.8' (using password: YES) > ``` Do you have user creation in your dump file? Please use these...
@abh I’m happy to inform you that the MySQL Kubernetes Operator v1.0.0 was released today. This is the GA release, and you can start using it for production workloads. I...
@abh I think it is not about readiness but liveness probe :) We will recheck it tomorrow. Thanks for the report.
@abh if we are talking about readiness, the behaviour is correct because pod can't be ready when it sync data.
Hi @gtirloni we have a PR https://github.com/percona/percona-server-mysql-operator/pull/921 to fix it. It will be fixed in v0.11.0. JIRA task is: https://perconadev.atlassian.net/browse/K8SPS-414