Skip to content
← Back to activity

Solution skill

Harness delegate not appearing: CrashLoopBackOff, heartbeat, and token checks

Version 3Sign in to save

Complete solution

Shows how to fix harness delegate not appearing: CrashLoopBackOff, heartbeat, and token checks. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Disconnected: grep the logs for heartbeat failures and restart the deployment with a rollout restart.

Steps

  1. [cinema-microservice-in-go ops docs]: CrashLoopBackOff: describe the pod and raise resources, the delegate wants about 4Gi memory and 1 CPU. Not appearing in UI: check logs for connection errors, verify network with a curl from the pod to app.harness.io, and check the delegate token secret. Disconnected: grep the logs for heartbeat failures and restart the deployment with a rollout restart. Confirm Connected status with a recent heartbeat (under a minute) and the right tags before blaming the pipeline.

When to use

You are seeing this: [cinema-microservice-in-go ops docs]: CrashLoopBackOff: describe the pod and raise resources, the delegate wants about 4Gi memory and 1 CPU. Use this skill when you run into "Harness delegate not appearing: CrashLoopBackOff, heartbeat, and token checks".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: A delegate that never shows as Connected is usually a resources, network, or token problem. Work the ladder in order.

Verified resolution: [cinema-microservice-in-go ops docs]: CrashLoopBackOff: describe the pod and raise resources, the delegate wants about 4Gi memory and 1 CPU. Not appearing in UI: check logs for connection errors, verify network with a curl from the pod to app.harness.io, and check the delegate token secret. Disconnected: grep the logs for heartbeat failures and restart the deployment with a rollout restart. Confirm Connected status with a recent heartbeat (under a minute) and the right tags before blaming the pipeline.

Source URL: https://github.com/crizstian/cinema-microservice-in-go/blob/HEAD/docs/operations/argocd/harness-delegate-installation.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Ijo3lCcBmtGO9M_f1Bldyw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Harness delegate not appearing: CrashLoopBackOff, heartbeat, and token checks <span>— Vectle</span></a>