[object Object][object Object][object Object]

After ClusterD starts, the following ConfigMaps are created:

• [object Object]. For details, see .
• [object Object]. For details, see . [object Object] is an integer that increments from 0. For every additional 1,000 nodes in a cluster, a new ConfigMap file of this type is created.
• [object Object]. For details, see . [object Object] is an integer that increments from 0. For every additional 2,000 nodes in a cluster, a new ConfigMap file of this type is added.

Table 1 cluster-info-node-cm

[object Object][object Object]

[object Object]undefined

Table 2 cluster-info-device-${m}

[object Object][object Object]

[object Object]undefined

Table 3 cluster-info-switch-${x}

[object Object][object Object]

[object Object]undefined[object Object]

This ConfigMap is located in the user-created [object Object] namespace, with the label [object Object]. It is used to display fault information in a cluster (currently only common fault information is displayed).

Table 4 Data information

[object Object]undefined

[object Object]

[object Object]

This ConfigMap is located in the user-created [object Object] namespace, with the label [object Object].

Table 5 super-pod-<super-pod-id>

[object Object]undefined[object Object]

This ConfigMap is located in the [object Object] namespace created by the user. It is used to display fault job information that requires forced release of communication resources in the cluster. It takes effect only when process-level rescheduling is performed on the Atlas 900 A3 SuperPoD.

Table 6 fault-job-info

[object Object]undefined[object Object]

This ConfigMap is located in the [object Object] namespace created by the user. It is used to display the chips and fault information of manual isolation in the cluster.

The following is an example:

Table 7 clusterd-manual-info-cm

[object Object]undefined