Allow user configurable probes for streaming and worker Deployments
Nobody has claimed this yet.
- #10 by @jstewart612 — closed without merging
- Dominant language
- Mustache
- Stars
- 197
- Forks
- 104
- Avg merge
- 22m
- Merged PRs (30d)
- 2
Description
Pitch
I'd like to be able to, using the first-party Mastodon Helm Chart, configure my liveness, readiness, and startup probes on Deployment objects to meet my needs of my running environment.
Motivation
People who want to either do more advanced probes and checking for health, or users who want to customize probes to operate Mastodon in slower environments are two examples that immediately spring to mind.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the first-party Mastodon Helm chart's values and the templates for the streaming and worker Deployment objects. Determine how probe settings are currently defined, then verify that liveness, readiness, and startup probes can be configured for both Deployments and that the rendered manifests reflect those settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100