Restoration Job fails to get agent endpoint when there are multiple replicas for a service/pod
hsubramanianaks opened this issue · 0 comments
Is your feature request related to a problem? Please describe.
Restoration Job fails to get agent endpoint when there are multiple replica sets for a service/pod
Mention what platform you want to support the new feature
all platforms
Describe the solution you'd like
Restoration job need to identify the pod and get the agent endpoint successfully.
Pass the selected pod name while creating restoration job in a config map which would save a http call to k8s api to find out the pod name.
2023-11-08T23:42:29.2836387Z | RestorationJob | WARNG | Found 2 pods for deployment todoapp/stats-api but expected 1
2023-11-08T23:42:29.2838679Z | RestorationJob | TRACE | Event: RestorationJob-AgentPing {"eventName":"RestorationJob-AgentPing","properties":{"RestorePerformed":"false","NumFailedPings":"2","HasConnectedClients":"","Result":"Failed"},"metrics":{"DurationInMs":23}}