Merge pull request #239388 from omkark95/main

[Azure Arc K8s] Update to troubleshooting guide

Author: prmerger-automator[bot]

articles/azure-arc/kubernetes/troubleshooting.md

@@ -43,27 +43,42 @@ If the Helm Chart release is present with `STATUS: deployed`, check the status o
 
 ```console
 $ kubectl -n azure-arc get deployments,pods
-NAME                                       READY  UP-TO-DATE  AVAILABLE  AGE
-deployment.apps/clusteridentityoperator     1/1       1          1       16h
-deployment.apps/config-agent                1/1       1          1       16h
-deployment.apps/cluster-metadata-operator   1/1       1          1       16h
-deployment.apps/controller-manager          1/1       1          1       16h
-deployment.apps/flux-logs-agent             1/1       1          1       16h
-deployment.apps/metrics-agent               1/1       1          1       16h
-deployment.apps/resource-sync-agent         1/1       1          1       16h
-
-NAME                                            READY   STATUS  RESTART  AGE
-pod/cluster-metadata-operator-7fb54d9986-g785b  2/2     Running  0       16h
-pod/clusteridentityoperator-6d6678ffd4-tx8hr    3/3     Running  0       16h
-pod/config-agent-544c4669f9-4th92               3/3     Running  0       16h
-pod/controller-manager-fddf5c766-ftd96          3/3     Running  0       16h
-pod/flux-logs-agent-7c489f57f4-mwqqv            2/2     Running  0       16h
-pod/metrics-agent-58b765c8db-n5l7k              2/2     Running  0       16h
-pod/resource-sync-agent-5cf85976c7-522p5        3/3     Running  0       16h
+NAME                                         READY   UP-TO-DATE   AVAILABLE   AGE
+deployment.apps/cluster-metadata-operator    1/1     1            1           3d19h
+deployment.apps/clusterconnect-agent         1/1     1            1           3d19h
+deployment.apps/clusteridentityoperator      1/1     1            1           3d19h
+deployment.apps/config-agent                 1/1     1            1           3d19h
+deployment.apps/controller-manager           1/1     1            1           3d19h
+deployment.apps/extension-events-collector   1/1     1            1           3d19h
+deployment.apps/extension-manager            1/1     1            1           3d19h
+deployment.apps/flux-logs-agent              1/1     1            1           3d19h
+deployment.apps/kube-aad-proxy               1/1     1            1           3d19h
+deployment.apps/metrics-agent                1/1     1            1           3d19h
+deployment.apps/resource-sync-agent          1/1     1            1           3d19h
+
+ 
+
+NAME                                              READY   STATUS    RESTARTS        AGE
+pod/cluster-metadata-operator-74747b975-9phtz     2/2     Running   0               3d19h
+pod/clusterconnect-agent-cf4c7849c-88fmf          3/3     Running   0               3d19h
+pod/clusteridentityoperator-79bdfd945f-pt2rv      2/2     Running   0               3d19h
+pod/config-agent-67bcb94b7c-d67t8                 1/2     Running   0               3d19h
+pod/controller-manager-559dd48b64-v6rmk           2/2     Running   0               3d19h
+pod/extension-events-collector-85f4fbff69-55zmt   2/2     Running   0               3d19h
+pod/extension-manager-7c7668446b-69gps            3/3     Running   0               3d19h
+pod/flux-logs-agent-fc7c6c959-vgqvm               1/1     Running   0               3d19h
+pod/kube-aad-proxy-84d668c44b-j457m               2/2     Running   0               3d19h
+pod/metrics-agent-58fb8554df-5ll67                2/2     Running   0               3d19h
+pod/resource-sync-agent-dbf5db848-c9lg8           2/2     Running   0               3d19h
 ```
 
 All pods should show `STATUS` as `Running` with either `3/3` or `2/2` under the `READY` column. Fetch logs and describe the pods returning an `Error` or `CrashLoopBackOff`. If any pods are stuck in `Pending` state, there might be insufficient resources on cluster nodes. [Scaling up your cluster](https://kubernetes.io/docs/tasks/administer-cluster/) can get these pods to transition to `Running` state.
 
+### Resource Provisioning Failed 
+If you receive this error, it indicates that there was an error due to which the resource could not be provisioned successfully. Please check the status of the Azure Arc enabled Kubernetes service at the following dashboard: [Azure status](https://azure.status.microsoft/en-us/status). If the status is healthy and you continue to face issues while onboarding, please raise a support ticket. If the status is unhealthy, please wait until the status becomes healthy and try onboarding again after deleting the existing connected cluster Azure resource.
+
+### Service Timeout 
+If you receive this error, it indicates that the service timed out while provisioning the certificates. Please check the status of the Azure Arc enabled Kubernetes service at the following dashboard: [Azure status](https://azure.status.microsoft/en-us/status). If the status is healthy and you continue to face issues while onboarding, please raise a support ticket. If the status is unhealthy, please wait until the status becomes healthy and try onboarding again after deleting the existing connected cluster Azure resource.
 
 ### Overage claims error