Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restoration Job fails to get agent endpoint when there are multiple replicas for a service/pod #337

Open
hsubramanianaks opened this issue Nov 8, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@hsubramanianaks
Copy link
Collaborator

hsubramanianaks commented Nov 8, 2023

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}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog Features
1 participant