Develop plan for keeping Elasticsearch version up to date on GitLab.com
Background
We need to determine when we want to upgrade Elasticsearch version on GitLab.com. Currently this determination has been a manual process and I'd love to discuss how we can automate it.
Some considerations:
- Must keep compatible with OpenSearch
- Breaking changes potential
- Want to keep on a supported version
Ideas on what could be automated
Example issue with work required: #109 (closed)
- open required MRs for updating the version and assign to team members for ownership/review:
- CI for
gitlab
- CI for
gitlab-elasticsearch-indexer
- gdk version
- QA nightly testing pipelines.
- CI for
- open infrastructure change request MR, assign to team members for review
- minor upgrade script (will make calls to ElasticCloud?)
- major upgrade script (will make calls to ElasticCloud?)
Edited by Terri Chu