-
Notifications
You must be signed in to change notification settings - Fork 772
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
Implement a restart endpoint #342
Comments
I would like to give try on it. |
What should an endpoint look like? I understand the underlying process, but what should the endpoint's response be? |
Hey @patelajay745, response of the endpoint can simply be 200 OK without the body if there was no error, or 500 Internal server error with the error in the response body. You can map the error in the response using |
Ok. Got it about response. How should endpoint look like? |
I was thinking about {
"group": "...",
"version": "...",
"kind": "...",
"name": "...",
"namespace": "..."
} |
Got it . Thanks |
Is your feature request related to a problem? Please describe.
To allow users to restart their workloads, cyclops-ctrl should expose a restart endpoint. You can register the endpoint and its handler function here.
The endpoint should receive the group, version, kind, name and the namespace of the resource that needs to be restarted. You can fetch those similarly to how it was done here. You can also check this link on how to restart a resource using go-client here.
Scope of the issue is implementing only the backend endpoint. Frontend part will be implemented separately.
The text was updated successfully, but these errors were encountered: