Cody (Xuecheng) Zhang
Cody (Xuecheng) Zhang
/test pull-e2e-kind-across-kubernetes
/test pull-e2e-kind-across-kubernetes
/merge
The above is just some warn logs, are there more logs?
but the `continue` wouldn't block reconciliation, https://github.com/pingcap/tidb-operator/blob/v1.5.1/pkg/manager/volumes/sync_volume_status.go#L79-L82
@adamtwiss have you tried to specify the config as the ".ini'/TOML format in the YAML file? our current recommended format is TOML and in fact we should update the examples...
As TiDB Operator has some defaulting logic it will update the TidbCluster object. But if we handle this defaulting logic carefully, we may avoid unnecessary updates to the object.
/run-pull-e2e-kind
/cherry-pick release-1.5
This is caused by the `job_name` mismatch of TidbMonitor (Prometheus) and Dashboard promQL. You can try to use `configMapRef` of TidbMonitor to mount an external ConfigMap to overwrite the default...