Logging: Cleanup database of `clusters_applications_elastic_stacks` & `clusters_integration_elasticstack` tables
Why are we doing this work
In %15.0, we disabled/removed pod logs by moving it behind a feature flag. After the feature flag is disabled & all application code is removed, the database can be purged of any of the old logging/elastic stack content.
Tracking issue for all logging removal work: Monitor:Logging Deprecation (#346485 - closed)
Relevant links
- https://docs.gitlab.com/ee/development/migration_style_guide.html#dropping-a-database-table [can be done in a post-migration in same release as removes all app code]
- https://docs.gitlab.com/ee/development/database/avoiding_downtime_in_migrations.html#dropping-tables
Implementation plan
- Ensure all dependent application code has been removed
- Drop
clusters_applications_elastic_stacks
, clusters_integration_elasticstack tables in a post-migration - clean up database dictionary records
- Include ~"group::configure" in code review
Note: global search is not related.
Edited by Sarah Yasonik