OpenSearch

Searching a large collection of documents or logs requires more than storing the original files. OpenSearch builds indexes that make that data searchable and supports queries and analysis over the indexed records. Teams use it for application search and for exploring operational data, with OpenSearch Dashboards providing a related user interface. Its storage layout, mappings and retention rules affect both usefulness and cost. It has its own releases and plugins, so replacing an Elasticsearch image is not a complete migration plan.

Chart ownership

The OpenSearch project hosts its community chart repository and publishes the OpenSearch and OpenSearch Dashboards charts through opensearch-project.github.io/helm-charts. Follow the installation guide for the selected release. Recent versions require a custom strong administrator password when bootstrapping the demo security configuration.

Before adoption

Replace demonstration credentials and certificates with the team's security configuration before wider access. Plan shard layout, storage capacity, snapshots and index retention; adding pods alone does not validate recovery or query performance. Test indexing and searches with realistic mappings and data, including loss of a node. Coordinate chart, application, Dashboards and plugin versions. If migrating from Elasticsearch or choosing the separate OpenSearch Operator, evaluate those migration and resource-ownership paths explicitly.