To run multiple instances of tabby, each instance will require its own persistent volume for logs and models. For source code indexes, there can be different mechanisms. You can either run indexing individually for each instance or have a worker build the index and distribute it through NFS. To configure tabby so that repo indexing is not done automatically, but only on request, you can run tabby scheduler --now manually.