[BUG] syncer:0.4.0 unable to parse the cluster[spec.componentSpecs.instances]

[duanhui8]

Describe the bug
test the instance template functionality, but Syncer 4.0 is unable to parse the cluster, resulting in the failure of the MySQL cluster startup.

To Reproduce
Steps to reproduce the behavior:

1. kubectl edit cluster xx
   componentSpecs:

• componentDefRef: mysql
  disableExporter: true
  enabledLogs:
  • auditlog
  • error
  • slow
    **instances:
  • env:
    • name: test_myintancetemplate
      value: my test instancetemplate
      name: test
      replicas: 1**

2. ClusterController, ComponentController, and InstanceSetController can correctly parse the instance template and update the corresponding pod templates, but Syncer 0.4.0 unable to parse the cluster and fails to start with an error(all pod).
   3、error:
   2025-01-14T17:55:59+08:00 INFO HA Get Cluster failed. {"cluster-name": "t1", "error": "json: cannot unmarshal object into Go struct field ClusterComponentSpec.spec.componentSpecs.instances of type string"}

Expected behavior
Syncer starts normally, can parse the cluster, and successfully starts the MySQL instance.

Screenshots

Desktop (please complete the following information):

• OS: centos8
• Kubernetes: v1.31.0
• Version kb0.9.2 syncer:0.3.9&&syncer:0.4.0

[duanhui8]

this is cluster.yaml

[xuriwuyun]

If instances are used in the cluster, the generated pod name should start from the maximum index of other pods. This can be achieved by specifying the unexpected pod name in offlineInstances.