konghui

@Mnicca 从message信息看，nacos服务的端口没有打开。在集群节点上访问http://172.17.0.3:8848/nacos/v1/ns/operator/servers看看能不能访问的通？ 如果还是不能访问的通需要查看对应的nacos节点的日志了，kubectl logs

这个pr可以解决该问题 https://github.com/nacos-group/nacos-k8s/pull/305 ``` apiVersion: nacos.io/v1alpha1 kind: Nacos metadata: name: nacos spec: ... k8sWrapper: PodSpec: imagePullSecrets: - name: myregistrykey ```

这个commit可以支持通用的k8s配置 https://github.com/shenkonghui/nacos-k8s/commit/3e292c3c23b535ad0f9f3ce34c444eaee5f252b2#diff-7f7439f4884279dd569a0c3714450d44f51ab5f072a5da19e3f4e219c2bf060b 测试结果如下 ``` $ kubectl get job nacos-mysql-sql-init -ojsonpath={.spec.template.spec.nodeSelector} {"disktype":"ssd"} $ kubectl get job nacos-mysql-sql-init -ojsonpath={.spec.template.spec.tolerations} [{"effect":"NoSchedule","key":"example-key","operator":"Exists"}] $ kubectl get sts nacos -ojsonpath={.spec.template.spec.nodeSelector} {"disktype":"ssd"}% $ kubectl get sts nacos...

@lczass 目前不支持自定义service名称。可以手动将service的yaml备份下来，修改后再创建。 你说的改pod名字是指？应该没法改元数据(名字)吧

 很多接口都是404

For the current recovery, I gave up binlog-replay. I downloaded binlog through binlog-fetch and then get binlog and pos with read xtrabackup_info , last use mysqlbinlog command to replay

In MYSQL, we use 'wal-g st put' to push latest binlog when this size is changed. you can refer to.