Files are fetched client-side and I didn't see any cache files being created server-side.

In T364473#9795007, @Fring wrote:

There's not much code to review here yet, but maybe it would make sense if someone else could clone the repo and test if the dev setup works for them as well. I'll hunt down someone for doing that in daily tomorrow.

• Create any missing indices
• Re-index all wikis starting from 2024-02-01

Waiting for cluster to stabilize again after expansion

Waiting on T359791

We split Elasticsearch's master and data nodes into their own GKE node pools and configured those pools to use a blue-green upgrade strategy. That way when a GKE node upgrade runs, only one Elasticsearch node will be taken down at a time. Since our Elasticsearch shards have node redundancy, search should continue to operate normally even with a slightly degraded cluster.