Folks - ArgoCD allows us to refer to clusters using IP or server however Harness only supports IP
IP
destination
namespace: rel-test-3
Server
destination:
namespace: rel-test-2
name: prod-cluster-us-west1
In a cloud environment where IPs change and systems are ephemeral - hard coding IPs is problematic. We're run into several instances where our cluster's IPs have changed on the backend forcing us to update all of the apps in Argo. We need the native ability of ArgoCD to use server (cluster) name to avoid problems in the future.