<p>Hi I was just trying to install argo CD in my local machine. I have  installed and running minikube.</p>
<p>After creating argocd namespace, I just try these commands</p>
<pre><code>kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

</code></pre>
<p>This error persists:</p>
<pre><code>Unable to connect to the server: dial tcp [2405:200:1607:2820:41::36]:443: i/o timeout

</code></pre>
<p>Could I get some help? Byw I'm new to argo...</p>

perarasan
<p>Play with argocd in the killercoda playground. This is probably the easiest way to get started learning and messing around with it.
<a href="https://killercoda.com/mabusaa/course/argocd-endusers-scenarios/00-argocd-playground" rel="nofollow noreferrer">https://killercoda.com/mabusaa/course/argocd-endusers-scenarios/00-argocd-playground</a></p>
<p>Or follow a guide like this:
<a href="https://dev.to/abhinavd26/all-about-argocd-a-beginners-guide-33c9" rel="nofollow noreferrer">https://dev.to/abhinavd26/all-about-argocd-a-beginners-guide-33c9</a></p>
<p>Make sure your endpoints and services are up and you can curl the endpoint. Make sure to read the sections about ingresses and where to curl or connect to.</p>
<p>You may also need to ensure your network is set up properly to allow you to access the endpoint.</p>
<p>Here is a quick example from running the killercoda example...</p>
<pre class="lang-bash prettyprint-override"><code>$ kubectl create namespace argocd
namespace/argocd created

$ kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
customresourcedefinition.apiextensions.k8s.io/applications.argoproj.io created
...
networkpolicy.networking.k8s.io/argocd-server-network-policy created
</code></pre>
<p>Look for the <code>argocd-server</code> pod to be running (bottom one)</p>
<pre class="lang-bash prettyprint-override"><code>$ kubectl get pods --namespace argocd
NAME                                                READY   STATUS    RESTARTS   AGE
argocd-application-controller-0                     1/1     Running   0          55s
argocd-applicationset-controller-84c8d6fc9b-nstm5   1/1     Running   0          55s
argocd-dex-server-59dc6fc75b-d8pnz                  1/1     Running   0          55s
argocd-notifications-controller-5d7dd8c5b7-j2hb4    1/1     Running   0          55s
argocd-redis-74cb89f466-52d22                       1/1     Running   0          55s
argocd-repo-server-c456f6997-4qcww                  1/1     Running   0          55s
argocd-server-7555f5c778-fx2s5                      1/1     Running   0          55s
</code></pre>
<p>Look at the endpoints - note the <code>argocd-server</code> endpoint on <code>192.168.1.21:8080</code></p>
<pre class="lang-bash prettyprint-override"><code>$ kubectl --namespace argocd get endpoints
NAME                                      ENDPOINTS                                               AGE
argocd-applicationset-controller          192.168.1.18:8080,192.168.1.18:7000                     85s
argocd-dex-server                         192.168.1.20:5558,192.168.1.20:5557,192.168.1.20:5556   85s
argocd-metrics                            192.168.1.23:8082                                       85s
argocd-notifications-controller-metrics   192.168.1.19:9001                                       85s
argocd-redis                              192.168.1.22:6379                                       85s
argocd-repo-server                        192.168.1.17:8084,192.168.1.17:8081                     85s
argocd-server                             192.168.1.21:8080,192.168.1.21:8080                     85s
argocd-server-metrics                     192.168.1.21:8083                                       85s
</code></pre>
<p>Look at the services - note the <code>argocd-server</code> service with <a href="https://kubernetes.io/docs/concepts/services-networking/cluster-ip-allocation/" rel="nofollow noreferrer">ClusterIP</a> 10.105.38.254 port(s) 80/TCP,443/TCP</p>
<pre class="lang-bash prettyprint-override"><code>$ kubectl --namespace argocd get service 
NAME                                      TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
argocd-applicationset-controller          ClusterIP   10.107.62.45     &lt;none&gt;        7000/TCP,8080/TCP            113s
argocd-dex-server                         ClusterIP   10.102.41.206    &lt;none&gt;        5556/TCP,5557/TCP,5558/TCP   113s
argocd-metrics                            ClusterIP   10.111.77.173    &lt;none&gt;        8082/TCP                     113s
argocd-notifications-controller-metrics   ClusterIP   10.100.24.197    &lt;none&gt;        9001/TCP                     113s
argocd-redis                              ClusterIP   10.100.133.38    &lt;none&gt;        6379/TCP                     113s
argocd-repo-server                        ClusterIP   10.106.117.208   &lt;none&gt;        8081/TCP,8084/TCP            113s
argocd-server                             ClusterIP   10.105.38.254    &lt;none&gt;        80/TCP,443/TCP               113s
argocd-server-metrics                     ClusterIP   10.98.252.11     &lt;none&gt;        8083/TCP                     113s
</code></pre>
<p>If you curl the argocd server cluster ip and port (10.105.38.254:443) or endpoint (192.168.1.21:8080), you should get something like this:</p>
<pre class="lang-bash prettyprint-override"><code>$ curl -k https://192.168.1.21:8080/swagger-ui
&lt;!DOCTYPE html&gt;
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;API documentation&lt;/title&gt;

                &lt;meta charset=&quot;utf-8&quot;/&gt;
                &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1&quot;&gt;
                &lt;link href=&quot;https://fonts.googleapis.com/css?family=Montserrat:300,400,700|Roboto:300,400,700&quot; rel=&quot;stylesheet&quot;&gt;

    
    &lt;style&gt;
      body {
        margin: 0;
        padding: 0;
      }
    &lt;/style&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;redoc spec-url='/swagger.json'&gt;&lt;/redoc&gt;
    &lt;script src=&quot;/assets/scripts/redoc.standalone.js&quot;&gt; &lt;/script&gt;
  &lt;/body&gt;
&lt;/html&gt;
</code></pre>
<p>If the curl responds, you can try to put the url in your browser and see if it connects. Otherwise look at the options in step 3 of this url for exposing the service (<a href="https://argo-cd.readthedocs.io/en/stable/getting_started/" rel="nofollow noreferrer">https://argo-cd.readthedocs.io/en/stable/getting_started/</a>)</p>
<pre class="lang-bash prettyprint-override"><code>$ kubectl port-forward svc/argocd-server -n argocd 8080:443
</code></pre>
