Delegate registration and verification
To set up a Harness Delegate, you install the delegate in your environment and the delegate automatically registers with your Harness account.
The delegate config file (for example, Kubernetes delegate YAML file) contains your Harness account Id. That's how the delegate knows where to register.
Install and register delegates
To install a delegate, follow the steps in the relevant delegate installation topic, such as Install a Kubernetes delegate or Install a Docker delegate.
Once you have installed the delegate in your environment, select Verify in the delegate wizard, and Harness will verify that it is receiving heartbeats from the delegate.
This means Harness is waiting for the delegate you installed to register. Registration can take a few minutes. Once the delegate registers, the Verify screen will indicate that the delegate is running.
Verify delegate registration manually
The Verify screen also includes troubleshooting steps. Here are a few of the steps for the Kubernetes delegate.
Check the status of the delegate on your cluster:
kubectl describe pod <your-delegate-pod> -n harness-delegate-ng
Check the delegate logs:
kubectl logs -f <harness-delegate> -n harness-delegate-ng
If the pod isn't up, you might see the following error in your cluster:
CrashLoopBackOff: Kubernetes Cluster Resources are not available.
Make sure the Kubernetes Cluster Resources (CPU, memory) are sufficient.
If the delegate didn't reach a healthy state, run the following:
kubectl describe pod <your-delegate-pod> -n harness-delegate-ng
Allowlist verification
Currently, allowlist verification for delegate registration is behind the feature flag PL_ENFORCE_DELEGATE_REGISTRATION_ALLOWLIST. Contact Harness Support to enable the feature.
With this feature flag enabled, delegates with an immutable image type can register if their IP/CIDR address is included in the allowed list received by Harness Manager.
Without this feature flag enabled, delegates with an immutable image type can register without allowlist verification.
The IP address/CIDR should be that of the delegate or the last proxy between the delegate and Harness Manager in the case of a proxy.
Harness Manager verifies registration requests by matching the IP address against an approved list and allows or denies registration accordingly. For more information, go to Add and manage IP allowlists.