You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@renchap some of the initial startup probes were too slow to work in rpi based k3s environment. I've since moved on from rpis so I don't really care if this happens now, but I am of the mind there is no good reason to forbid the user the right to change these parameters for themselves as may suit their operating needs.
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.
The text was updated successfully, but these errors were encountered: