<p>I have web services running in the GKE Kubernetes Engine. I also have monitoring services running in the cloud that are monitoring these services. Everything is working fine....except that I don't know how to access the Prometheus, and Kibana dashboards. I know I can use <strong>port-forward</strong> to temporarily forward a local port and access that way but that cannot scale with more and more engineers using the system. I was thinking of a way to provide access to these dashboards to engineers but not sure what would be the best way.</p>
<ol>
<li>Should I create a load balancer for each of these?</li>
<li>What about security? I only want a few engineers to have access to these systems.</li>
</ol>
<p>There are other considerations as well, would love to get your thoughts.</p>

<blockquote>
<p>Should I create a load balancer for each of these?</p>
</blockquote>
<p>No, you can create but not a good idea.</p>
<blockquote>
<p>What about security? I only want a few engineers to have access to
these systems.</p>
</blockquote>
<p>You can create an account in Kibana and manage access or else you can use the <strong>IAP</strong> <code>(Identity-Aware Proxy)</code> to restrict access. <a href="https://codelabs.developers.google.com/codelabs/user-auth-with-iap#0" rel="nofollow noreferrer">Ref doc</a></p>
<p>You have multiple options. You can use the LoadBalancer as you used but not a good idea though.</p>
<p>A good way to expose different applications is using the <strong>ingress</strong>. So i you are running the <strong>Prometheus</strong>, <strong>Jaeger</strong>, and <strong>Kibana</strong> in your <strong>GKE</strong>.</p>
<p>You can create the different hosts with <strong>domain prom.example.com</strong>, <strong>tracing.example.com</strong>, <strong>kibana.example.com</strong> so there will be <strong>single ingress controller</strong> service with type <strong>LoadBalancer</strong> and you can map <strong>IP</strong> to <strong>DNS</strong>.</p>
<p><a href="https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer#creating_an_ingress_resource" rel="nofollow noreferrer">Ref doc</a></p>
