title: How to get prometheus to run in a private GKE cluster
body: <p>I have a customer who has a security policy such that they only use private clusters in GKE.</p>
  <p>I have been trying to install the kube-prometheus-stack into their private clusters but I hit an issue.</p>
  <p>The first thing I did was to pull all the images that were in external repo such as quay.io and then push them to an Artifact repo set up for the project.</p>
  <p>I set the prometheus specific repos to be public so no secret is needed to access them.</p>
  <p>Then I pulled the helm chart and updated the values files to point to the new repo for all the images that seem to be needed by this helm chart.</p>
  <p>Now when I run the helm install it seems to work ok but when I am missing two of the pods that normally exist in a standard install.</p>
  <p>The pods that are missing are:</p>
  <ul>
  <li>alertmanager-kube-prometheus-kube-prome-alertmanager-0</li>
  <li>prometheus-kube-prometheus-kube-prome-prometheus-0</li>
  </ul>
  <p>I checked that the containers they use are present in the artifact repository and that all seems fine.</p>
  <p>There are no errors logged so it's hard to figure out why it isn't trying to start these pods.</p>
  <p>Does anyone know why it might not start up these two pods when there is no external internet access?</p>