<p>I am completely new to Kubernetes and having a lot of issues setting up Jenkins. Most of the issues I have gone through and solved though this one is killing me. For some reason, my Jenkins instance is not spawning new instances to run the jobs.</p>
<p>I have installed Jenkins using Helm (<a href="https://hub.helm.sh/charts/stable/jenkins" rel="nofollow noreferrer">https://hub.helm.sh/charts/stable/jenkins</a>). Below is my values configuration file:</p>
<pre class="lang-yaml prettyprint-override"><code>master:
  installPlugins:
    - kubernetes:1.12.6
    - workflow-job:2.24
    - workflow-aggregator:2.5
    - credentials-binding:1.16
    - git:3.9.1
  runAsUser: 0
  fsGroup: 0
  cpu: &quot;2&quot;
  numExecutors: 0
  memory: &quot;3500Mi&quot;
  javaOpts: &quot;-Xms3500m -Xmx3500m&quot;
  serviceType: NodePort
  hostName: *my-domain*
  ingress:
    enabled: true
    hostName: *my-domain*
    annotations:
      kubernetes.io/tls-acme: &quot;true&quot;
      kubernetes.io/ingress.class: &quot;nginx&quot;
      cert-manager.io/cluster-issuer: &quot;letsencrypt-prod&quot;
    tls:
      - secretName: jenkins-tls-secret
agent:
  enabled: true
  image: &quot;jenkins/jnlp-slave&quot;
  tag: &quot;3.27-1&quot;
  workingDir: &quot;/home/jenkins&quot;
  componentName: &quot;jenkins-slave&quot;
  resources:
    requests:
      cpu: &quot;512m&quot;
      memory: &quot;512Mi&quot;
    limits:
      cpu: &quot;512m&quot;
      memory: &quot;512Mi&quot;
</code></pre>
<p>I have setup the kubernetes plugin and a new cloud node 'Kubernetes' with not changes to any of the values (as per a suggestion i found online). When I test connection, everything works perfectly.</p>
<p>Inside the logs for Jenkins, i only see 1 weird thing:</p>
<pre><code>2020-07-13 15:32:45.746+0000 [id=94]    INFO    o.c.j.p.k.KubernetesClientProvider$SaveableListenerImpl#onChange: Invalidating Kubernetes client: kubernetes null
</code></pre>
<p>I have no idea on how to further debug the issue due to my lack of experience in Kubernetes. I have searched all across google but cant find anything that fixes this issue. Hopefully someone can help!</p>

Michael Guimaraes
<p>It seems like the cause of the issue was due to the kubernetes configuration not having the correct tunnel and URL</p>
