PingFederate only sends traffic to pingdirectory-0 #4
Description
Symtoms:
- If you stand up the stack from kustomize and start running tests on PF>PD, all traffic goes to pingdirectory-0 ( the first pd)
Cause + notes:
- PF seems to dns query the pd service and then store returned IPs for traffic. So if PF starts when only the first pd is available, it becomes locked on that one only.
- going in the admin console and changing the pd host and replicating changes only makes it worse!
Resolution:
PF engine init should wait for PF admin and all PDs to be available.
Temporary workaround:
- restart the PF stack after PD is running.