The module lifecycle stage: Preview
The module has requirements for installation
Release notes
v0.0.6
| Date | 2026-11-19 |
| Module | managed-opensearch |
| Version | 0.0.6 |
Summary
OpenSearch 3.9.0 and user synchronization status The new UsersSynced condition shows whether declared users and their roles have been applied, including after credential Secret changes. This release also upgrades OpenSearch from 3.7.0 to 3.9.0 and addresses known vulnerabilities.
Highlights
- UsersSynced reports whether declared users and their roles have been applied. Credential Secret changes do not require a resource edit or a pod restart.
- OpenSearch was upgraded from 3.7.0 to 3.9.0 with matching plugins and the Temurin 25.0.5+8 Java runtime.
- Go and Java dependencies were updated to address known vulnerabilities. All Go binaries are built with Go 1.27.4.
- Unsupported security auditing is explicitly disabled, preventing startup errors caused by a missing audit destination.
- Search templates no longer accept Mustache partials ({{>name}}). Replace them with inline content; ordinary template parameters remain supported.
v0.0.5
| Date | 2026-11-12 |
| Module | managed-opensearch |
| Version | 0.0.5 |
Summary
Added user management with the predefined roles ReadOnly, ReadWrite and Monitoring, the analysis-icu plugin for multilingual text analysis, and opensearch-custom-codecs for Zstandard index compression. Instance monitoring now provides access to metrics and statistics dashboards in the UI when enabled.
Highlights
- For new instances, declare application users and connect with their credentials over HTTP or HTTPS. Enabling TLS encrypts the connection; disabling it does not remove authentication requirements.
- Existing instances that previously ran without TLS retain anonymous access during the transition period, even if TLS is enabled later. Existing
admincredentials remain valid. Move applications to declared users before the planned removal ofadminand anonymous access in a future release. - Specify a positive
spec.instance.persistentVolumeClaim.sizewhen creating an instance. Existing volumes are not resized by the upgrade; storage can only be expanded. - Allow additional resources per instance beyond
spec.instance: requests of100mCPU and128Mimemory, and limits of500mCPU and256Mimemory. - analysis-icu plugin: ICU analyzers, tokenizers and filters are available for use in index mappings and analysis settings without additional plugin installation.
- opensearch-custom-codecs plugin: zstandard compression is opt-in: the default codec and existing indices are unchanged. When using custom codecs, retain compatible plugin support when upgrading, rolling back or restoring snapshots.
v0.0.4
| Date | 2026-10-22 |
| Module | managed-opensearch |
| Version | 0.0.4 |
Summary
A maintenance release that fixes editing of the OpenSearch configuration fields in the UI and validates service names early. The class allowlist now uses the same field names as the configuration users see.
Highlights
- Users can edit the configuration fields allowed by the administrator again: OpensearchClass.spec.overridableConfiguration uses the same field names as Opensearch.spec.configuration.
- An Opensearch name that is too long or not valid for a Kubernetes Service is rejected when the resource is created instead of failing later.
Fixes
- Configuration fields allowed in the OpensearchClass could not be edited by users because the allowlist used setting keys instead of field names; overridableConfiguration is now specified by configuration field names
- Invalid Opensearch names are rejected at creation (at most 49 characters, Kubernetes Service naming rules)
Documentation
- Resource name rules and the field-name form of overridableConfiguration are documented
v0.0.3
| Date | 2026-10-21 |
| Module | managed-opensearch |
| Version | 0.0.3 |
Summary
Managed OpenSearch now lets you tune key OpenSearch settings directly in the service resource, and administrators can set class-wide values. Changes take effect immediately on the running instance, and the service status shows when the new configuration has been applied.
The status conditions are now built from reconcile phase reports and the live workload state, so they reflect what is happening to the instance more accurately.
Highlights
The new conditions logic in the Opensearch status removes the race between controllers and reflects the service state more accurately.
- Tune the aggregation bucket limit and automatic index creation without restarting the instance.
- Administrators set class-wide values and choose which of them users may override in the OpensearchClass.
- The maximum HTTP request size is derived from the memory available to the instance.
- Status conditions report whether the instance runs the requested configuration.
- Deleting a service now always completes cleanly, even if its class was removed earlier.
New features
- Per-service OpenSearch configuration in Opensearch.spec.configuration, with class-wide values and the allowed set of user overrides defined by the administrator in the OpensearchClass
- Settings are applied to the running instance without a restart; the maximum HTTP request size is sized automatically from the instance memory
Improvements
- Status conditions are aggregated from reconcile phase reports and the live workload state, and reflect when the requested configuration is in effect
Fixes
- Fixed sizing validation on Opensearch update and the finalizer hanging when the OpensearchClass was already deleted
- Deleting a service no longer recreates the admin Secret
Documentation
- Each configuration setting is documented with its default value
v0.0.2
| Date | 2026-09-03 |
| Module | managed-opensearch |
| Version | 0.0.2 |
Summary
This release extends how an OpenSearch instance is exposed and observed. TLS can now use a user-provided certificate, clients can be required to present certificates, and monitoring can be tuned per instance.
Highlights
- Two TLS modes: a certificate issued by cert-manager or your own certificate from a Secret.
- Mutual TLS: client certificates are verified against your CA or the cluster Istio CA.
- Per-instance monitoring mode, including monitoring without alerts.
- The default class ships reworked sizing policies.
New features
spec.tlssupports theCertManagerandCustomCertificatemodes.spec.mTLSenables client certificate verification with a CA from a Secret or from Istio.spec.observabilityselects the monitoring mode:Enabled,DisabledorEnabledWithoutAlerts.
Improvements
- The default
OpensearchClasssizing policies are 1-4 cores with 2-8Gi and 5-16 cores with 8-32Gi.
Fixes
- The default
OpensearchClassno longer carries an undeclaredtopologyblock.
v0.0.1
| Date | 2026-06-29 |
| Module | managed-opensearch |
| Version | 0.0.1 |
Summary
First release of the Managed OpenSearch module. It deploys and manages standalone OpenSearch instances in a DKP cluster.
Highlights
- Standalone OpenSearch instances are created with the
Opensearchresource. - Administrators define allowed resources and validation rules in
OpensearchClass. - CPU and memory can be changed without recreating the instance.
- HTTPS with a cert-manager certificate; the admin password is kept in a Secret.
New features
- Standalone (single-node) OpenSearch instances via the
Opensearchresource with CPU, memory and disk settings. OpensearchClasstemplates with allowed CPU, memory and disk ranges and custom CEL validation rules.- Admission webhooks validate every create and update: resource ranges, no disk shrink, no
storageClassNamechange. - CPU and memory resize without recreating the instance; the JVM heap follows the memory limit.
- HTTPS with a server certificate issued by cert-manager; without TLS the instance runs in HTTP mode for development and smoke tests.
- The service state is reported in the conditions of the
Opensearchresource status. - OpenSearch and operator images are based on distroless; OpenSearch 3.7.0.