What Is The Correct Setting For Docker Delegate Deployment For Harness CD-community Edition?

Harness Knowledge Base
, , , ,
1

Module

  • Harness Continuous Delivery

Environment

  • Personal laptop(Windows, MacOS or Linux ), bare metal, containers,

Issue

I was testing the Harness CD-community edition and got an issue with the delegate deployment. I tried replacing the URL values of http://host.docker.internal:7143 with https://my.internal.instance/ but now the readiness probe is failing for some reason.

Can I know the correct settings for the following values? (these are the defaults it spits out):

- name: MANAGER_HOST_AND_PORT
value: http://host.docker.internal:7143
- name: WATCHER_STORAGE_URL
value: http://host.docker.internal:7143/storage/wingswatchers
- name: WATCHER_CHECK_LOCATION
value: watcherprod.txt
- name: DELEGATE_STORAGE_URL
value: http://host.docker.internal:7143/storage/wingsdelegates
- name: DELEGATE_CHECK_LOCATION
value: delegateprod.txt

Resolution

You should set the harness_host variable to https://my.internal.instance/ before you install Harness, to generate the correct delegate config. You can refer to the Advanced Configuration section of the install readme file for docker-compose and Helm.

2

I ran into this same issue installing CDCE on a VM. After seeing this post, I stopped the Harness manager, removed all Docker images, exported my HARNESS_HOST variable, and pulled down new Harness CDCE images. The delegate file still shows http://host.docker.internal.
I’m trying to run the delegate on the same VM as the CDCE Harness manager, but I don’t think that’s causing an issue at this point. The Harness manager is producing the same delegate yaml even after I exported the env var. Any guidance on how to fix this?