This is a fork of the opensearch-k8s-operator that was formerly hosted by Opster and is now part of the opensearch-project. Due to confusion and instability in the project, MaibornWolff has decided to (temporarily) provide a fork of the operator with compatible and stable releases. Feel free to open an issue or start a discussion if you have questions.
The Kubernetes OpenSearch Operator is used for automating the deployment, provisioning, management, and orchestration of OpenSearch clusters and OpenSearch dashboards.
The Operator can be easily installed using helm on any CNCF-certified Kubernetes cluster. Please refer to the User Guide for installation instructions.
- Deploy a new OS cluster.
- Ability to deploy multiple clusters.
- Spin up OS dashboards.
- Configuration of all node roles (master, data, coordinating..).
- Scale the cluster resources (manually), per nodes' role group.
- Drain strategy for scale down.
- Version updates.
- Change nodes' memory allocation and limits.
- Secured installation features.
- Certificate management.
- Rolling restarts - through API.
- Scaling nodes' disks - increase disk size.
- Cluster configurations and nodes' settings updates.
- Operator Monitoring, with Prometheus and Grafana.
The Operator can be easily installed using Helm:
- Add the helm repo:
helm repo add opensearch-operator https://maibornwolff.github.io/opensearch-operator/ - Install the Operator:
helm install opensearch-operator opensearch-operator/opensearch-operator
The operator aims to be compatible with all current and supported Opensearch 2.x versions. When a new Opensearch version comes out it might take some time for the operator to support specific features, but in general all 2.x versions should work. Note that the operator will not prevent you from running any version, regardless of if it was tested or not.
If you want to develop the operator, please see the separate developer docs.
We welcome contributions! See how you can get involved by reading CONTRIBUTING.md.