Provide basic guidelines for Zoekt on SM instances
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Background
We currently run Zoekt on GitLab.com production and offer a Beta for Self-Managed customers. However, we don't have any guidance for upgrades and scalability like how we do for Elasticsearch.
Proposal
We should consider expanding our documentation to include:
- General scalability guidance
- Usage or at least a reference to it in architecture documentation
- For example, our reference architecture includes a link to choosing your optimal cluster configuration
- The chart install instructions are not explicit and you can make some assumptions based on the defaults
- Information around migrations or required checks for upgrade procedures (this may be none)
Edited by 🤖 GitLab Bot 🤖