This article is meant to cover basic checks while troubleshooting an Automation Suite cluster
Prerequisites – Enabling kubectl
Before running any checks, enable kubectl access by switching to root user and setting the required environment variables:
sudo su -
export KUBECONFIG="/etc/rancher/rke2/rke2.yaml" \
&& export PATH="$PATH:/usr/local/bin:/var/lib/rancher/rke2/bin"Note: This must be done on a control plane (server) node. These variables are session-scoped, so they will need to be re-applied if you open a new terminal session.
1. Check Node Status
Purpose: Verifies that all nodes in the cluster are healthy, in Ready state, reachable by the control plane, and available for workload scheduling.
kubectl get nodes
```
Sample output:
NAME STATUS ROLES AGE VERSION
node-01 Ready control-plane,etcd,master 30d v1.27.4+rke2r1
node-02 Ready worker 30d v1.27.4+rke2r1
node-03 NotReady worker 30d v1.27.4+rke2r1
node-04 Ready,SchedulingDisabled worker 30d v1.27.4+rke2r1</code></pre>
<h2></h2>
<h2><span style="font-size: 14px;">#node-01 is an server node, is in Healthy state</span></h2>
<h2><span style="font-size: 14px;">#node-02 is an agent node, is in Healthy state</span></h2>
<h2><span style="font-size: 14px;">#node-03 is an agent node, is in UnHealthy state</span></h2>
<h2><span style="font-size: 14px;">#node-02 is an agent node, is in Healthy state (existing pods may run on it but still impacted), Cordoned (no new resources can be started on the node)</span></h2>
<h2><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<h2><span style="font-size: 14px;"><span style="font-family: Symbol;">·</span><span style="font-family: 'Times New Roman';"> </span><strong style="font-family: 'Courier New';">NotReady</strong> – The node is unhealthy and not communicating properly with the control plane. This requires immediate investigation. Connect using ssh on the affected node. Common causes include a stopped rke2-server/rke2-agent service, disk pressure, or network issues.</span></h2>
<h2><span style="font-size: 14px;"><span style="font-family: Symbol;">·</span><span style="font-family: 'Times New Roman';"> </span><strong style="font-family: 'Courier New';">SchedulingDisabled</strong><strong> (Cordoned)</strong> – The node has been cordoned, meaning no new pods will be scheduled onto it. Existing workloads may be impacted if there is insufficient capacity on remaining nodes. Verify whether the cordon was intentional (e.g., during maintenance). If not, uncordon the node with: </span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>kubectl uncordon <node-name></code></pre>
<h2><span style="font-size: 14px;"><span style="font-family: Symbol;">·</span><span style="font-family: 'Times New Roman';"> </span><strong>Any other unexpected status</strong> – Investigate on a case-by-case basis using following command to review events and conditions.</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>kubectl describe node <node-name></code></pre>
<h2></h2>
<h2><span style="font-size: 14px;">2. Check RKE2 Service Status</span></h2>
<h2><span style="font-size: 14px;"><strong>Purpose: </strong>Confirms that the RKE2 server process is actively running on a control plane node. This check should only be performed when a node has reported NotReady in the previous step, and it must be run directly on the affected node via SSH.</span></h2>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">systemctl status rke2-server</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">active (running)</code></strong> – The service is healthy. The issue may be network-related or tied to a kubelet problem. For recent logs.</span></h2>
</li></ul>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code> journalctl -u rke2-server --since "10 minutes ago"</code></pre>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">inactive (dead)</code> or <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">failed</code></strong> – The service has stopped or crashed. Restart it with:</span></h2>
</li></ul>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10"> </div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> systemctl stop rke2-server<br> rke2-killall.sh<br> systemctl start rke2-server </code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">Then monitor the status and check logs for the root cause:</span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative">
<div class="absolute inset-0 flex items-center justify-center"> </div>
</div>
</div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> journalctl -u rke2-server -f</code></span></pre>
</div>
<p class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Note:</strong> For worker nodes, the service name is <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rke2-agent</code>. Use <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">systemctl status rke2-agent</code> and restart with <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">systemctl restart rke2-agent</code> accordingly.</span></p>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">For advanced troubleshooting steps when rke2 service is not healthy follow steps from bellow article: <a href="https://uipath.lightning.force.com/lightning/r/Knowledge__kav/ka0Pa000000tf8yIAA/view" target="_blank">RKE2 Stuck In Activating</a> . If issue still persist generate an RKE2-SupportBundle.</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">3. Check for Crashed or Unhealthy Pods</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Purpose:</strong> Identifies pods across all namespaces that are not in a healthy running or completed state. This is particularly useful when a specific application or service is unreachable — a crashed pod is often the direct cause.</span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative">
<div class="absolute inset-0 flex items-center justify-center"> </div>
</div>
</div>
</div>
<div class="text-text-500 font-small p-3.5 pb-0"> </div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl get pods -A -o wide <span class="token token" style="color: #14181f;">|</span> <span class="token token" style="color: #0051c2;">grep</span> -v Running <span class="token token" style="color: #14181f;">|</span> <span class="token token" style="color: #0051c2;">grep</span> -v Completed
``<span class="token token" style="color: #b34a00;">`</span><span class="token token" style="color: #b34a00;">
</span>
**Sample output:**
<span class="token token" style="color: #b34a00;"></span><span class="token token" style="color: #b34a00;">`</span>``
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
uipath orchestrator-6df9b8c-xqz2p <span class="token token" style="color: #008080;">0</span>/1 CrashLoopBackOff <span class="token token" style="color: #008080;">14</span> 2h <span class="token token" style="color: #008080;">10.42</span>.1.15 node-02
uipath auth-service-7bc44d-lkj98 <span class="token token" style="color: #008080;">0</span>/1 Pending <span class="token token" style="color: #008080;">3</span> 45m <span class="token token" style="color: #008080;">10.42</span>.2.8 node-03</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">CrashLoopBackOff</code></strong> – The container is repeatedly crashing. Check the pod logs to identify the root cause:</span></h2>
</li></ul>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl describe pod <pod-name> -n <namespace> <br>kubectl logs <span class="token token" style="color: #14181f;"><</span>pod-name<span class="token token" style="color: #14181f;">></span> -n <namespace></code></span></pre>
</div>
<h2><span style="font-size: 14px;">For checking the logs for specific container: </span></h2>
<h2 class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl logs <span class="token token" style="color: #14181f;"><</span>pod-name<span class="token token" style="color: #14181f;">></span> -n <namespace> -c <container-name></code><strong></strong><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]"></code></strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Pending</code></strong> – The pod cannot be scheduled. This may be due to insufficient resources or a cordoned node. Use <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">kubectl describe pod -n <namespace> <pod-name></code> to view scheduling events.</span></h2>
</li><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Error</code> / <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">ImagePullBackOff</code></strong> – Investigate using <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">kubectl describe pod</code> for detailed event messages. Common causes include issues with the registry. </span></h2>
</li><li style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong><code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">OOMKilled</code></strong> – The pod exceeded its memory limit and was killed. Review resource limits and investigate a memory leak.</span></h2>
</li></ul>
<p class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Note:</strong> If a specific service (e.g., Orchestrator) is inaccessible, check whether its pod appears in this output. A crashed pod for that service confirms where to focus your log investigation.</span></p>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">4. Check Istio Ingress Gateway Status</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Purpose:</strong> Confirms that the Istio ingress gateway pods are running and fully ready on all nodes. Istio handles all inbound traffic routing into the cluster. If the ingress gateway is down or degraded, users will experience connectivity issues across the platform.</span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative"> </div>
</div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl -n istio-system get pods <span class="token token" style="color: #14181f;">|</span> <span class="token token" style="color: #0051c2;">grep</span> ingressgateway
``<span class="token token" style="color: #b34a00;">`</span><span class="token token" style="color: #b34a00;">
</span>
**Sample output:**
<span class="token token" style="color: #b34a00;"></span><span class="token token" style="color: #b34a00;">`</span>``
NAME READY STATUS RESTARTS AGE
istio-ingressgateway-7d456f9b8-abc12 <span class="token token" style="color: #008080;">1</span>/1 Running <span class="token token" style="color: #008080;">0</span> 5d
istio-ingressgateway-7d456f9b8-def34 <span class="token token" style="color: #008080;">1</span>/1 Running <span class="token token" style="color: #008080;">0</span> 5d</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>All pods show <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">1/1 Running</code></strong> – Istio is healthy.</span></h2>
</li><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>Any pod shows <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">0/1</code> or is not in <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Running</code> state</strong> – This should be treated as an <strong>active outage</strong>. Users will likely be unable to reach platform services. Investigate immediately:</span></h2>
</li></ul>
<h2><span style="font-size: 14px;">To enable istio logging see <a href="https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide/how-to-enable-istio-logging" target="_blank">How to Enable Istio logging</a></span></h2>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> kubectl describe pod -n istio-system <span class="token token" style="color: #14181f;"><</span>pod-name<span class="token token" style="color: #14181f;">></span>
kubectl logs -n istio-system <span class="token token" style="color: #14181f;"><</span>pod-name<span class="token token" style="color: #14181f;">></span></code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">Escalate if the pod cannot be recovered through a restart:</span></h2>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> kubectl rollout restart deploy/istiod -n istio-system<br> kubectl rollout restart ds/istio-ingressgateway -n istio-system</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">5. Check RKE2 CoreDNS Status</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Purpose:</strong> Confirms that CoreDNS pods are running and healthy. CoreDNS is responsible for all internal DNS resolution within the cluster. If it is down, pods will be unable to resolve service names, causing widespread connectivity failures across the platform.</span></h2>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl -n kube-system get pods <span class="token token" style="color: #14181f;">|</span> <span class="token token" style="color: #0051c2;">grep</span> coredns <span class="token token" style="color: #14181f;">|</span> <span class="token token" style="color: #0051c2;">grep</span> -v autoscaler
``<span class="token token" style="color: #b34a00;">`</span><span class="token token" style="color: #b34a00;">
</span>
**Sample output:**
<span class="token token" style="color: #b34a00;"></span><span class="token token" style="color: #b34a00;">`</span>``
NAME READY STATUS RESTARTS AGE
rke2-coredns-coredns-abc <span class="token token" style="color: #008080;">1</span>/1 Running <span class="token token" style="color: #008080;">0</span> 10d
rke2-coredns-coredns-def <span class="token token" style="color: #008080;">1</span>/1 Running <span class="token token" style="color: #008080;">0</span> 10d</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>All CoreDNS pods show <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">1/1 Running</code></strong> – DNS is healthy.</span></h2>
</li><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>CoreDNS pods are not ready or crashing</strong> – This is likely caused by a <strong>checksum offload issue</strong> with the Cilium CNI plugin, which is a known issue in RKE2 environments. Resolve it by disabling checksum offloading and restarting Cilium, fix should be made persistent via a system startup script see <a href="https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide/how-to-disable-tx-checksum-offloading" target="_blank">How to disable TX checksum offloading</a></span></h2>
</li></ul>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10"> </div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"><span class="token token" style="color: #6e7687;"> # Restart the Cilium pods</span>
kubectl -n kube-system rollout restart daemonset cilium</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">After restarting, re-run the CoreDNS check to confirm pods return to <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">1/1 Running</code>. </span></h2>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">6. Check Cilium Status</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Purpose:</strong> Confirms that Cilium, the CNI (Container Network Interface) plugin responsible for all pod networking and network policy enforcement, is healthy. If Cilium is degraded, pods will experience network connectivity issues, and in severe cases the entire cluster network can be disrupted.</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Step 1 – Get a Cilium pod name:</strong></span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative">
<div class="absolute inset-0 flex items-center justify-center"> </div>
</div>
</div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl -n kube-system get pods -l k8s-app<span class="token token" style="color: #14181f;">=</span>cilium</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Step 2 – Exec into a Cilium pod and check status:</strong></span></h2>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl -n kube-system <span class="token token" style="color: #b34a00;">exec</span> -it <strong><span class="token token" style="color: #14181f;"><</span>cilium-pod-name<span class="token token" style="color: #14181f;">></span></strong> -- cilium status<br>kubectl -n kube-system exec -it <strong><span class="token token" style="color: #14181f;"><</span>cilium-pod-name<span class="token token" style="color: #14181f;">> -- </span></strong>cilium status | grep -E "KVStore|Kubernetes:|Cilium:|Cilium health|Routing|Proxy Status|Hubble|Cluster health|Controller Status"</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Step 3 – Check Cilium network health:</strong></span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative"> </div>
</div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl -n kube-system <span class="token token" style="color: #b34a00;">exec</span> -it <strong><span class="token token" style="color: #14181f;"><</span>cilium-pod-name<span class="token token" style="color: #14181f;">></span></strong> -- cilium-health status</code></span></pre>
</div>
<h2><span style="font-size: 14px;">All fields show <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">OK</code> and all nodes show <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">OK</code> connectivity – Cilium is healthy. No action required.</span></h2>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">7. Check Ceph Storage Status</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Purpose:</strong> Confirms that the Ceph distributed storage cluster and its RADOS Gateway (RGW) pods are healthy. Ceph provides persistent storage for the platform. A full outage occurs when <strong>both</strong> RGW gateway pods are down simultaneously — if only one is down, the system may degrade but continue functioning.</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Step 1 – Confirm Ceph is in use:</strong></span></h2>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl get ns rook-ceph</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">If this command returns a result, Ceph is deployed in this environment and you should proceed with the checks below. If the namespace is not found, Ceph is not in use and this check can be skipped as Customer is using an external object store (S3 compatible).</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Step 2 – To check if ceph is healthy or not, you can run :</strong></span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>kubectl -n rook-ceph exec deploy/rook-ceph-tools -- ceph status</code></pre>
<h2><span style="font-size: 14px;">This will show output as below</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>cluster:
id: 18c99f48-222f-468b-b9d3-656728acdb27
health: HEALTH_OK
services:
mon: 3 daemons, quorum a,b,c (age 6h)
mgr: b(active, since 7h), standbys: a
osd: 3 osds: 3 up (since 7h), 3 in (since 7h)
rgw: 2 daemons active (2 hosts, 1 zones)
data:
pools: 9 pools, 89 pgs
objects: 22.70k objects, 3.1 GiB
usage: 11 GiB used, 85 GiB / 96 GiB avail
pgs: 89 active+clean
io:
client: 79 KiB/s rd, 511 B/s wr, 39 op/s rd, 26 op/s wr</code></pre>
<h2><span style="font-size: 14px;">If there is any issue with ceph, above command will display the issue with message.</span></h2>
<h2><span style="font-size: 14px;">You can further check the detail error using below command</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>kubectl exec -it -n rook-ceph deploy/rook-ceph-tools -- ceph health detail</code></pre>
<h2><span style="font-size: 14px;">Above command will give detailed error message.<strong></strong></span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Step 3 – Check the status of Ceph pods:</strong></span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>kubectl get pod -n rook-ceph
Sample output:
NAME READY STATUS RESTARTS AGE
rook-ceph-mgr-a-77b7d6ff89-hdndp 2/2 Running 0 14h
rook-ceph-mgr-b-5bf758d68f-7t5kz 2/2 Running 0 14h
rook-ceph-mon-a-7cc8c6f96f-2rh5d 1/1 Running 0 14h
rook-ceph-mon-b-7f6d7897fb-2d7mk 1/1 Running 0 14h
rook-ceph-mon-c-5c7c4f6f9-78r9x 1/1 Running 0 14h
rook-ceph-operator-54c85h9fdf-jldtq 1/1 Running 0 14h
rook-ceph-osd-0-557c9b5f4b-7zktb 0/1 Init:Error 0 03s
rook-ceph-osa-1-b/btt8b48b-JJ/bz 1/1 Running 0 14h
rook-ceph-osd-2-558d7fc6ff-9tw89 1/1 Running 0 14h
rook-ceph-rgw-rook-ceph-a-697cf44cb5-c7jws 1/1 Running 0 14h
rook-ceph-rgw-rook-ceph-b-59cff9c7f9-tbk2f 1/1 Running 0 14h
rook-ceph-tools-99d67b6d4-kvn7m 1/1 Running 0 14h
[root@server@~]#</code></pre>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>MON or OSD pods are not running</strong> – This indicates deeper storage infrastructure issues. Loss of monitor quorum (requires majority of MON pods to be running) or OSD failures can lead to data unavailability. </span></h2>
</li></ul>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">If the pods fail to recover, check the health of the underlying Ceph cluster components — particularly the monitors (<code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rook-ceph-mon-*</code>) and OSDs (<code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rook-ceph-osd-*</code>).</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">In case of multinode, an osd can be rebuild from a healthy one.</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">A failing monitor quorum or unavailable OSDs can prevent the RGW from starting. </span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>One RGW pod is down</strong> – The system is degraded but should remain operational. Investigate the failing pod but this does not constitute a full outage:</span></h2>
</li></ul>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> kubectl describe pod -n rook-ceph <span class="token token" style="color: #14181f;"><</span>rgw-pod-name<span class="token token" style="color: #14181f;">></span>
kubectl logs -n rook-ceph <span class="token token" style="color: #14181f;"><</span>rgw-pod-name<span class="token token" style="color: #14181f;">></span></code></span></pre>
</div>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>Both RGW pods are down</strong> – Treat this as an <strong>active outage</strong>. Platform services relying on object storage will be unavailable. Attempt to recover by restarting the RGW deployment:</span></h2>
</li></ul>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> kubectl -n rook-ceph rollout restart deployment <span class="token token" style="color: #14181f;"><</span>rgw-deployment-name<span class="token token" style="color: #14181f;">></span></code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"></ul>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">8. Check Redis Status</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Purpose:</strong> Confirms that the Redis Enterprise Cluster (REC) and Redis Enterprise Databases (REDB) are healthy. Redis provides the caching and message brokering layer for Orchestrator and AiCenter. If Redis is down, <strong>Orchestrator will be unavailable</strong>.</span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative">
<div class="absolute inset-0 flex items-center justify-center"> </div>
</div>
</div>
</div>
<div class="overflow-x-auto">
<pre class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">kubectl -n redis-system get rec<br>NAME NODES SHARDS VERSION STATE SPEC STATUS LICENSE STATE LICENSE EXPIRATION DATE AGE<br>redis-cluster 1 1/1 7.22.2-20.focal Running Valid Valid 2032-01-30T00:00:00Z 17d<br><br><br>kubectl -n redis-system get redb<br>NAME VERSION PORT CLUSTER SHARDS STATUS SPEC STATUS AGE<br>redis-cluster-db 7.4.3 12000 redis-cluster 1 active Valid 17d<br><br><br>kubectl -n redis-system get pods<br>NAME READY STATUS RESTARTS AGE<br>redis-cluster-0 2/2 Running 0 63m<br>redis-cluster-recovery-job-29526325-vg6wt 0/1 Completed 0 9m58s<br>redis-cluster-recovery-job-29526330-txv9w 0/1 Completed 0 4m58s<br>redis-cluster-services-rigger-77cf75fff-qp64m 1/1 Running 0 15h<br>redis-enterprise-operator-6476977c4d-snzlq 2/2 Running 0 15h</code></span></pre>
</div>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings and remediation:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>REC state is <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Running</code></strong> – The Redis Enterprise Cluster is healthy.</span></h2>
</li><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>REDB status is <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">active</code></strong> – The database is healthy and available to Orchestrator.</span></h2>
</li><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>All pods are <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Running</code> or <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Completed</code></strong> – The Redis environment is fully operational.</span></h2>
</li></ul>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Findings that require action:</strong></span></h2>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"><li class="whitespace-normal break-words pl-2" style="font-size: 14px;">
<h2><span style="font-size: 14px;"><strong>REC state is not <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">Running</code></strong> – This is the primary indicator that Redis is unhealthy. Orchestrator will be down. </span></h2>
</li></ul>
<h2><span style="font-size: 14px;">Redis cluster can be rebuild using <a href="https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide/redis-probe-failure" target="_blank">Redis Probe Failure </a>doc page.</span></h2>
<div class="sticky opacity-0 group-hover/copy:opacity-100 top-2 py-2 h-12 w-0 float-right">
<div class="absolute right-0 h-8 px-2 items-center inline-flex z-10">
<div class="relative">
<div class="absolute inset-0 flex items-center justify-center"> </div>
</div>
</div>
</div>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">9. Check kernel and OS level settings (all cluster nodes):<strong></strong></span></h2>
<h2><span style="font-size: 14px;">Check that <strong>ip_forwarding</strong> is enabled , also disable <strong>reverse path filtering</strong>. </span></h2>
<h2 class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;">sysctl net.ipv4.ip_forward
``<span class="token token" style="color: #b34a00;">`</span>
**Sample output:**
<span class="token token" style="color: #b34a00;"></span><span class="token token" style="color: #b34a00;">`</span>``
<span class="token token" style="color: #6e7687;"># Enabled (expected)</span>
net.ipv4.ip_forward <span class="token token" style="color: #14181f;">=</span> <span class="token token" style="color: #008080;">1</span>
<span class="token token" style="color: #6e7687;"># Disabled (action required)</span>
net.ipv4.ip_forward <span class="token token" style="color: #14181f;">=</span> <span class="token token" style="color: #008080;">0</span></code></span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>
<h2 class="code-block__code !my-0 !rounded-lg !text-sm !leading-relaxed p-3.5" style="color: #14181f;font-family: var(--font-mono);"><span style="font-size: 14px;"><code class="language-bash" style="color: #14181f;font-family: var(--font-mono);white-space: pre;"> <span class="token token" style="color: #6e7687;"># Enable immediately (takes effect without a reboot)</span>
sysctl -w net.ipv4.ip_forward<span class="token token" style="color: #14181f;">=</span><span class="token token" style="color: #008080;">1</span>
<span class="token token" style="color: #6e7687;"># Make the change persistent across reboots</span>
cat <<EOF >>"/etc/sysctl.d/99-sysctl.conf"<br> net.bridge.bridge-nf-call-iptables = 1<br> net.ipv4.ip_forward = 1<br> net.bridge.bridge-nf-call-ip6tables = 1<br> net.ipv4.conf.all.rp_filter=0<br> EOF<br><br> <code>sysctl --system</code></code></span></h2>
<h2></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">Check <strong>fapolicy</strong> : </span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>systemctl status fapolicyd</code></pre>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">If the result is enable you need to disable it with the following command:</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>Systemctl stop fapolicyd
Systemctl disable fapolicyd</code></pre>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">see for details: <a href="https://uipath.my.salesforce-sites.com/CaseView/articles/Knowledge/RKE2-Fails-to-Start-If-fapolicyd-Is-Enabled?lang=en_US" target="_blank">RKE2 Fails To Start If fapolicyd Is Enabled</a></span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">Check <strong>Firewalld</strong>:</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>systemctl status firewalld</code></pre>
<h2><span style="font-size: 14px;">If the result of this command is enabled, it is required to disable it with the following commands:</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>Systemctl stop firewalld
Systemctl disable firewalld</code></pre>
<h2><span style="font-size: 14px;">Note: firewalld needs to be disable always in Automation Suite single or multi-node.</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">Check <strong>SELinux</strong>: </span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>getenforce
Sample output:
# SELinux is enforcing (action required)
Enforcing
# SELinux is permissive (action required)
Permissive
# SELinux is disabled (expected)
Disabled</code></pre>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">In order to disable it:</span></h2>
<pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code> # Make the change persistent across reboots
sed -i 's/^SELINUX=.*/SELINUX=disabled/' /etc/selinux/config
# Verify the change to the config file
grep '^SELINUX=' /etc/selinux/config
</code></pre>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">Restart the node. </span></h2>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">10. Check Certificates: </span></h2>
<h2><span style="font-size: 14px;">The article <a href="https://uipath.my.salesforce-sites.com/CaseView/articles/Knowledge/Certificates-validity-check-in-Automations-suite-with-script?lang=en_US" target="_blank">Certificates validity check in Automation Suite with script </a>can be used :</span></h2>
<h2><span style="font-size: 14px;"><strong>The script will verify the below certificates:</strong></span></h2>
<ol style="list-style-type: decimal;"><li style="font-size: 14px;">
<h2><span style="font-size: 14px;">Server</span></h2>
</li><li style="font-size: 14px;">
<h2><span style="font-size: 14px;">Identity</span></h2>
</li><li style="font-size: 14px;">
<h2><span style="font-size: 14px;">Webhook</span></h2>
</li><li style="font-size: 14px;">
<h2><span style="font-size: 14px;">Rke2 Rancher</span></h2>
</li></ol>
<h2></h2>
<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold"><span style="font-size: 14px;">Next Steps: </span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;">If the issue still persists after completing all of the above checks, please create a support bundle and a diagnostic report for further analysis.</span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><a href="https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide/running-the-diagnostics-tool#running-the-diagnostics-tool" target="_blank">Diagnostic Report</a></span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><a href="https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide/using-support-bundle-tool#using-the-automation-suite-support-bundle" target="_blank">Support Bundle</a></span></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>
<p class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><span style="font-size: 14px;"><strong>Note:</strong> This article contains as well a bash script ASCluster_Health_Check.sh that can be used to check automatically all the above.</span></p>
<h2></h2>
<h2 class="font-claude-response-body break-words whitespace-normal leading-[1.7]"></h2>