Make indexPerNamespace default for OpenSearch #2831
Description
Description
We have found that there are certain problems that are tricky to solve when components from apps share indexes with other applications deployed on top of Welkin. It can often be unfeasible to manage field mappings in a way that no conflicts arise, and thus we cannot ensure that no logs get rejected and dropped, including logs from apps components like falco.
Therefore, we should make indexPerNamespace for OpenSearch the default in Apps. This provides a nice separation between Apps components and any other applications, making things like index field mappings more manageable both for Platform Admins and App Developers, as there wont be conflicts between the two.
We should also make sure to look at the resource footprint and see if it changes significantly with indexPerNamespace enabled in a standard environment.
Public documentation will also need to be updated to be in accordance with ìndexPerNamespace as the new default.
Additional context
This may also open up some additional filtering for client_error metric/alerts (i.e. mapping conflicts in admin namespaces vs user namespaces). But that is not necessarily in scope for this task.
It may be wise to implement automatic retention configuration for indexPerNamespace as part of this task, or have it as a prerequisite.
Definition of done
- IndexPerNamespace is the new default for OpenSearch
- Resource footprint was checked with and without indexPerNamespace in a standard environment
- Public docs have been updated to reflect this change