OpenSearch

Deploy OpenSearch clusters on your Kubernetes cluster with Edka’s one click installation. Edka provisions them through the OpenSearch Kubernetes Operator with cert-manager, so the cluster, TLS, and OpenSearch Dashboards come up configured.

What Edka Provisions

Edka installs OpenSearch through the OpenSearch Kubernetes Operator and brings up a working cluster on infrastructure you control:

• Version: OpenSearch 3.7.0 (latest).
• Node Count: 3, 5, 7, or 9 nodes. The operator requires at least 3 cluster-manager nodes, and each node carries the cluster_manager, data, and ingest roles.
• Persistent Storage: A hcloud-volumes PersistentVolume per node from 10 GiB to 1 TB, set at install and resizable later.
• Generated Credentials: A password for the built-in admin user is generated and stored as a Kubernetes Secret, retrievable from the console.
• TLS: The operator issues certificates for both the transport (per-node) and HTTP layers.
• REST API Endpoint: A ClusterIP service on port 9200, reachable in cluster at https://opensearch.opensearch-system.svc.cluster.local:9200.

OpenSearch Dashboards

OpenSearch Dashboards ships alongside the cluster by default. Edka deploys a single Dashboards instance wired to the cluster, listening on port 5601, with a generated cookie secret that keeps browser sessions stable for the lifetime of the instance. Disable it from the console if you only need the REST API.

Configuration Options

Tune your deployment from the Edka console before or after install:

• Resources: Memory limit per node from 2 GB to 128 GB, CPU limit from 0.5 to 48 CPU, and the JVM heap size (set to roughly half the memory limit).
• Storage: Persistent volume size per node and storage class.
• Dashboards: Toggle OpenSearch Dashboards on or off and set its memory (1 GB to 4 GB) and CPU (0.5 to 4 CPU) limits.
• Access: Optionally publish Dashboards through an Envoy Gateway traffic class on your own hostname, with TLS from a matching Edka-managed wildcard or hostname certificate. A public hostname can fall back to Edka’s Gateway HTTP-01 issuer.

Getting Started

1. Click “Deploy OpenSearch” below.
2. Select your node count, per-node resources, and JVM heap size.
3. Choose storage size, keep Dashboards on or off, and optionally expose Dashboards through a Gateway hostname.
4. Deploy. Your cluster will be ready in a few minutes.
5. Retrieve the generated admin password from the console and sign in to OpenSearch Dashboards.

Deploy OpenSearch