<p><strong>Question</strong></p>

<p>Is it problematic to create two Services for the same pod, one for internal access and the other for external access?</p>

<p><strong>Context</strong></p>

<p>I have a simple app running on GKE.</p>

<p>There are two pods, each with one container:</p>

<ol>
<li>flask-pod, which runs a containerized flask app</li>
<li>postgres-pod, which runs a containerized postgres DB</li>
</ol>

<p>The flask app accesses the postgres DB through a ClusterIP Service around the postgres DB.</p>

<p><strong>Concern</strong></p>

<p>I also have connected a client app, TablePlus (running on my machine), to the postgres DB through a LoadBalancer Service. Now I have 2 separate services to access my postgres DB. Is this redundant, or can this cause problems?</p>

<p>Thanks for your help.</p>

<p>It is perfectly fine. If you look at StatefulSets, you define one headless service that is used for internal purpose and another service to allow access from clients.</p>
