Allow ArgoCD GitOps Agents to target clusters by name
this fiscal quarter
M
Marvellous Duck
Currently the ArgoCD Gitops Agent only allows Applications to target Server URLs via the "server" field in "destination" section.
ArgoCD allows to target clusters by their human-legible name which is a lot easier to configure and validate instead of server IP addresses.
Feature Request: Allow GitOps Applications in Harness to also support using "name" field to target GitOps clusters by name.
Log In
Canny AI
Merged in a post:
Harness should support server names in addition to IPs for cluster referencing
P
Pure Dinosaur
Folks - ArgoCD allows us to refer to clusters using IP or server however Harness only supports IP
IP
destination
server: 'https://10.212.0.157'
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.
C
Comprehensive Thrush
this fiscal quarter
Rohan Gupta
long-term
Adding this to our backlog thank you for your feature request.