Description of problem:

When enabling notifications, as per the online documentation, the notification pod is generated but using default argoCD argument where "argocd-repo-server:8081" is used as the default reposerver. But such a service does not exist, instead, a service called "<argocd instancename>-repo-server" is present.

Workaround

manually create the service "argocd-repo-server" pointing to the repo-server deployment:

oc expose deploy/openshift-gitops-repo-server -n openshift-gitops --name argocd-repo-server

Prerequisites (if any, like setup, operators/versions):

1.7,1.8

Steps to Reproduce

https://github.com/svghadi/argocd-operator/blob/notification-repo-addr-bug/tests/k8s/1-022_validate_notifications/reproducer.md 

Actual results:

This is the cause of the following error in the notification pod:

connection error: desc = \"transport: Error while dialing dial tcp: lookup argocd-repo-server on 172.28.0.10:53: server misbehaving

Expected results:

The notification should point the correct service.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

$ oc rsh -n openshift-gitops openshift-gitops-notifications-controller-798bd77576-7k6nd argocd-notifications --help 
[...]
      --argocd-repo-server string       Argo CD repo server address (default "argocd-repo-server:8081")
[...]

 *