<p>I am following the <code>Installation Instructions</code> from <a href="https://argoproj.github.io/argo-cd/getting_started/#3-access-the-argo-cd-api-server" rel="nofollow noreferrer">https://argoproj.github.io/argo-cd/getting_started/#3-access-the-argo-cd-api-server</a>
and even though the service type has been changes to <code>LoadBalancer</code> I cannot manage to login.</p>
<p>The information I have is:</p>
<pre><code>$ oc describe svc argocd-server
Name:                     argocd-server
Namespace:                argocd
Labels:                   app.kubernetes.io/component=server
                          app.kubernetes.io/name=argocd-server
                          app.kubernetes.io/part-of=argocd
Annotations:              &lt;none&gt;
Selector:                 app.kubernetes.io/name=argocd-server
Type:                     LoadBalancer
IP:                       172.30.70.178
LoadBalancer Ingress:     a553569222264478ab2xx1f60d88848a-642416295.eu-west-1.elb.amazonaws.com
Port:                     http  80/TCP
TargetPort:               8080/TCP
NodePort:                 http  30942/TCP
Endpoints:                10.128.3.91:8080
Port:                     https  443/TCP
TargetPort:               8080/TCP
NodePort:                 https  30734/TCP
Endpoints:                10.128.3.91:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   &lt;none&gt;
</code></pre>
<p>If I do:</p>
<pre><code>$ oc login https://a553569222264478ab2xx1f60d88848a-642416295.eu-west-1.elb.amazonaws.com
The server is using a certificate that does not match its hostname: x509: certificate is valid for localhost, argocd-server, argocd-server.argocd, argocd-server.argocd.svc, argocd-server.argocd.svc.cluster.local, not a553569222264478ab2xx1f60d88848a-642416295.eu-west-1.elb.amazonaws.com
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

error: Seems you passed an HTML page (console?) instead of server URL.
Verify provided address and try again.
</code></pre>

<p>If you wish to expose an ArgoCD server via ingress, you can disable the TLS by  patching the argocd-server deployment:</p>
<p>no-tls.yaml</p>
<hr />
<pre><code>spec:
  template:
    spec:
      containers:
      - name: argocd-server
        command: 
          - argocd-server
          - --insecure
</code></pre>
<pre><code>kubectl patch deployment -n argocd argocd-server --patch-file no-tls.yaml 
</code></pre>
