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.

Sign up for GitHub

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

Jump to bottom

Add a startupProbe to Reaper deployments #66

Closed
Miles-Garnsey opened this issue Aug 23, 2021 · 1 comment
Closed

Add a startupProbe to Reaper deployments #66

Miles-Garnsey opened this issue Aug 23, 2021 · 1 comment
Labels
enhancement New feature or request needs-triage

Comments

@Miles-Garnsey
Copy link
Member

Miles-Garnsey commented Aug 23, 2021 •
edited by sync-by-unito bot
Loading

Is your feature request related to a problem? Please describe.

At present, when Reaper starts, it is frequently restarted while running the migration process. It appears that it does not return liveness probes during this this process.

We could use a startupProbe in addition to the liveness probe to avoid unneccesary container churn and improve startup times.

Describe the solution you'd like
Add a startup probe to the Reaper deployment.

┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: K8SSAND-830
┆Priority: Medium
@Miles-Garnsey Miles-Garnsey added enhancement New feature or request needs-triage labels Aug 23, 2021
@Miles-Garnsey
Copy link
Member Author

It looks like this is already fixed under #57. Don't mind me 😳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request needs-triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Miles-Garnsey