We've had situations during the roadshow when parksmap will not pick up the mlbparks service with type=parksmap-backend.
Behavior seems to relate to when the Watcher scans and finds the new mlbparks service with type=parksmap-backend, but the pod is not yet available. parksmap will then sometimes trigger exception (i'm guessing timing?). When the mlbparks service is up and ready, it doesn't show on the map and the Watcher no longer picks up the mlbparks service. If parksmap is then scaled down (replicas=0) then back up, the new pod will pick up the endpoint.
This seems like it would be fixed with #3 which forces a endpoint refresh on page refresh?
We've had situations during the roadshow when parksmap will not pick up the mlbparks service with type=parksmap-backend.
Behavior seems to relate to when the Watcher scans and finds the new mlbparks service with type=parksmap-backend, but the pod is not yet available. parksmap will then sometimes trigger exception (i'm guessing timing?). When the mlbparks service is up and ready, it doesn't show on the map and the Watcher no longer picks up the mlbparks service. If parksmap is then scaled down (replicas=0) then back up, the new pod will pick up the endpoint.
This seems like it would be fixed with #3 which forces a endpoint refresh on page refresh?