Description of problem:

Discrepancy between Applicationset Controller Pod ContainerPort (8000) and Service TargetPort (8080) for metrics

Original Jira issue: https://issues.redhat.com/browse/GITOPS-2008

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

Steps to Reproduce

1. Install Gitops Operator 1.7.0-16 from one of the IIBs:

Index image v4.8: registry-proxy.engineering.redhat.com/rh-osbs/iib:370159
Index image v4.9: registry-proxy.engineering.redhat.com/rh-osbs/iib:370160
Index image v4.10: registry-proxy.engineering.redhat.com/rh-osbs/iib:370161
Index image v4.11: registry-proxy.engineering.redhat.com/rh-osbs/iib:370162
Index image v4.12: registry-proxy.engineering.redhat.com/rh-osbs/iib:370163

 2.  Check the containerPort value for metrics in openshift-gitops-applicationset-controller deployment (the value is 8000) :

$ oc get deployment.apps/openshift-gitops-applicationset-controller -o jsonpath='{.spec.template.spec.containers[].ports}' | jq
[
(...)
  {
    "containerPort": 8000,
    "name": "metrics",
    "protocol": "TCP"
  }
]

Argocd-operator code: https://github.com/argoproj-labs/argocd-operator/blob/master/controllers/argocd/applicationset.go#L227 

3. Check the targetPort value for metrics in openshift-gitops-applicationset-controller service (the value us 8080):

$ oc get service/openshift-gitops-applicationset-controller -o jsonpath='{.spec.ports}' | jq
[
(...)
  {
    "name": "metrics",
    "port": 8080,
    "protocol": "TCP",
    "targetPort": 8080
  }
]

Argocd-operator code: https://github.com/argoproj-labs/argocd-operator/blob/master/controllers/argocd/applicationset.go#L498

Actual results:

Different containerPort (8000) and  targetPort (8080) values

Expected results:

The same containerPort and {}targetPort

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

openshift-gitops-operator-bundle-container-v1.7.0-16

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