<p>Our registered Gitlab-runner (on Kubernetes) was working fine, after upgrading the version of Gitlab, it can't clone the projects anymore! Does anyone have any idea about this issue?</p>
<p>Here is the log of the issue:</p>
<pre><code>Running with gitlab-runner 14.9.0 (d1f69508)
  on gitlab-runner-dev K5KVWdx-
Preparing the &quot;kubernetes&quot; executor
30:00
Using Kubernetes namespace: cicd
Using Kubernetes executor with image &lt;docker-registry&gt;:kuber_development ...
Using attach strategy to execute scripts...
Preparing environment
30:07
Waiting for pod cicd/runner-k5kvwdx--project-1227-concurrent-02kqgq to be running, status is Pending
Waiting for pod cicd/runner-k5kvwdx--project-1227-concurrent-02kqgq to be running, status is Pending
    ContainersNotReady: &quot;containers with unready status: [build helper]&quot;
    ContainersNotReady: &quot;containers with unready status: [build helper]&quot;
Running on runner-k5kvwdx--project-1227-concurrent-02kqgq via gitlab-runner-85776bd9c6-rkdvl...
Getting source from Git repository
32:13
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/bigdata/search/query-processing-module/.git/
Created fresh repository.
fatal: unable to access '&lt;git-repository&gt;': Failed to connect to &lt;gitlab-url&gt; port 443 after 130010 ms: Operation timed out
Cleaning up project directory and file based variables
30:01
ERROR: Job failed: command terminated with exit code 1
</code></pre>

Mostafa Ghadimi
<p>Here is how I would debug this Issue:</p>
<ol>
<li>Make sure there are no <a href="https://kubernetes.io/docs/concepts/services-networking/network-policies/" rel="nofollow noreferrer">NetworkPolicies</a> present, that are restricting the egress of the pod.</li>
<li>If you have the newest Kubernetes version you can run an ephemeral debug container inside the Pod to examine the networking situation. <a href="https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/#ephemeral-container" rel="nofollow noreferrer">Docs</a></li>
</ol>
<pre class="lang-bash prettyprint-override"><code>kubectl debug -it ephemeral-demo --image=busybox:1.28 --target=ephemeral-demo
</code></pre>
<ol start="2">
<li>If not you can try to get a shell inside your container and examine the situation from there or you can try to start a pod on the same node and try to connect from there.</li>
</ol>
<p>As soon as you have a shell inside some container that doesn't work try to answer the following questions:</p>
<ul>
<li>Can you connect to some other Server?</li>
<li>Can you resolve the hostname?</li>
<li>Is the IP a private one and overlapping with some internal Kubernetes IPs?</li>
<li>Can you ping the IP? If yes
<ul>
<li>Can you curl the IP? If no
<ul>
<li>If you open another port on the target machine can you connect to this port? =&gt; if yes probably some firewall problem somewhere</li>
</ul>
</li>
</ul>
</li>
<li>If no (can't ping) =&gt; can be either firewall related or IP routing related.</li>
</ul>
<p>I cannot say for sure what is wrong, but try the steps above and hopefully you get some insight into where the Problem is.</p>
