title: Getting "x509: certificate signed by unknown authority" even with "--insecure-skip-tls-verify" option in Kubernetes
body: <p>I have a private Docker image registry running on a Linux VM (10.78.0.228:5000) and a Kubernetes master running on a different VM running Centos Linux 7.</p>
  
  <p>I used the below command to create a POD:<br>
  <code>kubectl create --insecure-skip-tls-verify -f monitorms-rc.yml</code></p>
  
  <p>I get this:</p>
  
  <blockquote>
    <p>sample   monitorms-mmqhm    0/1    ImagePullBackOff   0  8m</p>
  </blockquote>
  
  <p>and upon running:
  <code>kubectl describe pod monitorms-mmqhm --namespace=sample</code></p>
  
  <blockquote>
    <p>Warning Failed Failed to pull image "10.78.0.228:5000/monitorms":
    Error response from daemon: {"message":"Get
    <a href="https://10.78.0.228:5000/v1/_ping" rel="noreferrer">https://10.78.0.228:5000/v1/_ping</a>: x509: certificate signed by unknown
    authority"}</p>
  </blockquote>
  
  <p>Isn't Kubernetes supposed to ignore the server certificate for all operations during POD creation when the <code>--insecure-skip-tls-verify</code> is passed?</p>
  
  <p>If not, how do I make it ignore the tls verification while pulling the docker image?</p>
  
  <p><strong>PS:</strong></p>
  
  <p><strong>Kubernetes version :</strong></p>
  
  <p>Client Version: <code>v1.5.2</code>
  Server Version: <code>v1.5.2</code></p>
  
  <p>I have raised this issue here: <a href="https://github.com/kubernetes/kubernetes/issues/43924" rel="noreferrer">https://github.com/kubernetes/kubernetes/issues/43924</a></p>