<p>I have some servers I want to deploy in Kubernetes. The clients of those servers will also be in Kubernetes. Clients and servers can independently be deployed or scaled.</p>

<p>The clients must know the list of the servers (IPs). I have an HTTP endpoint on the clients to update the list of the servers while the clients are running (hot config reload).</p>

<p>All this is currently running outside of Kubernetes. I want to migrate to GCP.</p>

<p>What's the industry standard regarding pods updates and notifications? I want to get notified when servers are updated to call the endpoints on the clients to update the list of the servers.</p>

<p>Can't use a LoadBalancer since the clients really need to call a specific server (business logic are in the clients).</p>

<p>Thanks</p>

Mike Gleason jr Couturier
<p>The standard for calling a group of pods that offer a functionality is <a href="https://kubernetes.io/docs/concepts/services-networking/service/" rel="nofollow noreferrer">services</a>. If you don't want automated load-balancing or a single IP address, which regular services do, you should look into <a href="https://kubernetes.io/docs/concepts/services-networking/service/#headless-services" rel="nofollow noreferrer">headless services</a>. Calling headless services returns a list of DNS A records that point to the pods behind the service. This list is automatically updated as pods become available/unavailable.</p>
