I have a load balanced deployment of spring boot service A, say on a 3 node kubernetes cluster.
I also have a requirement to enable quick configuration management without needing to rebuild+deploy a full blown rebaked image.
For that I put together a spring boot config-server, as well as implemented the Actuator restart on service A which when calling its /restart endpoint on a local single instance deployment it refreshes and loads with the properties fetched from the config-server.
So far so good, but...
How can the above be achieved when service A is deployed on a larger scale k8s deployment with 3, 30 or 300 instances of service A?
Calling /refresh endpoint must be handled by the load balancer as any other REST call on the cluster, meaning it is routed to one of the service instances.
Is there a standard way in springboot-on-k8s I can call each service instance ignoring the LB?