Gitlab Kubernetes Agent - Push behaviour on self hosted runners inside cluster network

GitLab CI/CD
, ,
1

What I have set up:

  1. I have a kubernetes cluster on a private network with NAT internet access (cluster cannot be reached from outside the private network)
  2. I have registered the agent on gitlab successfully
  3. I have a Gitlab Runner on the same private network as the cluster
  4. I have registered the runner on gitlab successfully

Question:
Will the KUBECONFIG for the agent in the CI/CD pipeline work if my self hosted runner executes the pipeline job?

I know it wouldn’t work with a shared runner, because there is no external access to the cluster, but my own runner is on the same network as the cluster and thus should have access. I am not sure what address the KUBECONFIG would try to use to reach the cluster.