Supposeyouareanexpertinkubernetesandoperationandmaintenanceengineer,
pleaseusethefollowingerrorinformationtoanswerthequestion.Errorinformation: {
 "physical_cluster": "PC1",
 "children": {
  "physical_machine": "PM1",
  "events": ["Host Parent Partition CPU Utilization high",
  "CMB_ACS_PHY_EVENT_1020",
  "Cluster resource failed"],
  "process": ["2023-07-15 02:37:00 Cluster resource of storage pool in clustered roles failed on PM1 which need CPU resource to compute for new role assign",
  "2023-07-15 02:47:00 The parent partition CPU utilization is 100 and has exceeded the warning or critical levels for PM1",
  "2023-07-15 02:52:00 PM1 SMB delay high. event：File system operation has taken longer than expected."],
  "children": {
   "NAME_1": "NAME_2,NAME_3",
   "events": ["CMB_LINUX_NTP_TIME",
   "Kube_NAME_1_Unreachable",
   "Kube_NAME_1_Not_Ready",
   "CMB_Linux_OS_ process_hung_120s"],
   "process": ["2023-07-15 02:54:31 SSH is not available for NAME_2",
   "2023-07-15 03:00:30 NAME_2 has delayed for more than 30 seconds for Network Time Protocol",
   "2023-07-15 03:02:30 NAME_2,NAME_3 are not ready",
   "2023-07-15 03:00:00 there is a synchronization time exception for NAME_1 NAME_2,NAME_3",
   "2023-07-15 02:56:00 ACS virtual machine:Linux system was blocked for more than 120 seconds on NAME_2,NAME_3"],
   "children": {
    "pod": "pod1",
    "events"["Readiness_Probe_Failed",
    "Liveness_Probe_Failed"],
    "process": ["2023-07-15 02:54:32 Readiness Probe Failed for pod pod1,pod2",
    "2023-07-15 02:54:32 Liveness Probe Failed for pod pod1,pod3"],
    "children": {
     "application": app1,
     "events": ["App_Java_Net_Unknown_Exception_Host_Exceeded"],
     "process": ["2023-07-15 03:04:28 java.net.UnknownHostException is detected for more than 30 times on app1"]
    }
   }
  }
 }
}
relevant events(A->B means A might cause B): 
1.Cluster resource failed -> Host Parent Partition CPU Utilization high which indicates this storage cluster pool failed to assign a master NAME_1 so a new master NAME_1 needs to be calculated which might leed to high CPU consumption
2.Kube_NAME_1_Not_Ready -> Readiness_Probe_Failed indicates nodes which are not ready might cause the pods run on NAME_1 failed to prob readiness
3.Kube_NAME_1_Not_Ready -> Liveness_Probe_Failed indicates nodes which are not ready might cause the pods run on NAME_1 failed to prob liveness
4.CMB_Linux_OS_ process_hung_120s -> Kube_NAME_1_Not_Ready
Here is the explain of the json format:
Normally physical_machine is part of physical_cluster, NAME_1 is part of physical_machine and pod i Your answer should have exactly 6 paragraphs. Make sure that the last paragraph starts with the word "service" and that each paragraph is separated by two new lines.
user