Matthew Abbott

I agree that setting limits in a separate PR is worthwhile. I strongly second @renchap's opinion that limits should skew low as a counter to memory leaks within both web...

I wrote a Job resource that looks a lot like the existing job-db-migrate but with the relevant tootctl command and toggles for resetting chewy. I'll port that template down to...

@hardillb Take a look at #95. When upgrading to 4.2.0 the `resetChewy` flag should be `true`. I found a `concurrency` value of 10 to work well on my cluster but...

Yes, you should be able to manually run that command in any container running the webserver or sidekiq. Spinning up a dedicated container theoretically gives you the dual benefits of...

I have a couple things I've implemented in a wrapper chart for my instance, which may be beneficial to this new effort. I'll bring them up here since it looks...

It's possible that tag "v4.0" doesn't exist in the mastodon repo; try "v4.0.15" and see if that helps Two side suggestions, just in case you haven't thought of them: 1....

This addresses #87.

The intended use case is to deploy once with this enabled and then disable it before future chart deployments. This is a pattern we already use for other one-time jobs.

When you want to deploy search, you pass `--set 'matsodon.deploySearch.enabled=true'` at the command line, which overrides the setting in values.yaml for that single run. You can also change that setting...

The intention is [edit: as hardillb noted while I wrote this!] for pre-4.2 installations to run this on upgrade. IIRC a server installed post 4.2 with elasticsearch already working wouldn't...