Elasticsearch

Deploy Elasticsearch clusters on your Kubernetes cluster with Edka’s one click installation. Edka provisions them through the Elastic Cloud on Kubernetes (ECK) operator with cert-manager, so the cluster, TLS, and Kibana come up configured.

What Edka Provisions

Edka installs Elasticsearch through the ECK operator and brings up a working cluster on infrastructure you control:

• Version: Elasticsearch 9.1.5 (latest) or 8.19.5.
• Node Count: 1, 3, 5, 7, or 9 nodes. A single node carries the master, data, ingest, ml, remote_cluster_client, and transform 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 elastic user is generated and stored as a Kubernetes Secret.
• TLS: ECK issues certificates for the cluster’s internal traffic.
• REST API Endpoint: A ClusterIP service on port 9200, reachable in cluster at https://elasticsearch-es-http.elastic-system.svc.cluster.local:9200.

Kibana

Kibana ships alongside the cluster by default. Edka deploys a single Kibana instance wired to the Elasticsearch reference, listening on port 5601. 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. Host path storage is also available, with the tradeoff that data is tied to a specific node.
• Kibana: Toggle Kibana on or off and set its memory and CPU limits.
• Access: Optionally publish Kibana through an Envoy Gateway traffic class on your own hostname, with TLS from a cert-manager cluster issuer.

Getting Started

1. Click “Deploy Elasticsearch” below.
2. Select your version, node count, and per-node resources.
3. Choose storage size, and optionally expose Kibana through a Gateway hostname.
4. Deploy. Your cluster will be ready in 3-5 minutes.
5. Retrieve the generated elastic password from your cluster and access Kibana.

Deploy Elasticsearch