<p>I have installed Rancher 2 and created a kubernetes cluster of internal vm's ( no AWS / gcloud).</p>

<p>The cluster is up and running. We are behind Corp proxy.</p>

<p>1) Installed Kubectl and executed kubectl cluster-info . It listed my cluster information correctly.</p>

<p>2) Installed helm </p>

<p>3) Configured helm referencing <a href="https://rancher.com/docs/rancher/v2.x/en/installation/ha/helm-init/" rel="nofollow noreferrer">Rancher Helm Init</a> </p>

<p>4) Tried installing Jenkins charts via helm</p>

<pre><code> helm install --namespace jenkins --name jenkins -f values.yaml stable/jenkins
</code></pre>

<p>The values.yaml has proxy details.</p>

<pre><code>---
  Master:
    ServiceType: "ClusterIP"
    AdminPassword: "adminpass111"
    Cpu: "200m"
    Memory: "256Mi"
    InitContainerEnv:
      - name: "http_proxy"
        value: "http://proxyuserproxypass@proxyname:8080"
      - name: "https_proxy"
        value: "http://proxyuserproxypass@proxyname:8080"
    ContainerEnv:
      - name: "http_proxy"
        value: "http://proxyuserproxypass@proxyname:8080"
      - name: "https_proxy"
        value: "http://proxyuserproxypass@proxyname:8080"
    JavaOpts: &gt;-
      -Dhttp.proxyHost=proxyname
      -Dhttp.proxyPort=8080
      -Dhttp.proxyUser=proxyuser
      -Dhttp.proxyPassword=proxypass
      -Dhttps.proxyHost=proxyname
      -Dhttps.proxyPort=8080
      -Dhttps.proxyPassword=proxypass
      -Dhttps.proxyUser=proxyuser
  Persistence:
    ExistingClaim: "jk-volv-pvc"
    Size: "10Gi"
</code></pre>

<p>5) The workloads are created. However the Pods are stuck.Logs complains about SSL certificate verification.     </p>

<p>How to turn SSL verification off.  I dont see an option to set in values.yaml.
We cannot turn off installing plugins during deployment as well.</p>

<p>Do we need to add SSL cert when deploying charts?</p>

<p><a href="https://i.stack.imgur.com/RZ5TV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/RZ5TV.png" alt="enter image description here"></a></p>

<p>Any idea how to solve this issue? </p>

VVP
<p>I had the same issues as you had.  In my case it was due to the fact that my DNS domain had a wildcard A record.  So updates.jenkins.io.mydomain.com would resolve fine.  After removing the wildcard, that fails now, so the host will then properly interpret updates.jenkins.io, as updates.jenkins.io.</p>

<p>This is fully documented here:
<a href="https://github.com/kubernetes/kubernetes/issues/64924" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/64924</a></p>
