kubeblocks-engine-elasticsearch

Provision Elasticsearch on KubeBlocks with preflight validation and topology selection.

3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-engine-elasticsearch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubeblocks-engine-elasticsearch
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-engine-elasticsearch
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-engine-elasticsearch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured create-time entry for Elasticsearch on KubeBlocks, aligning topology, version, storage, and sizing to reduce guesswork and ensure environment readiness.

Core Features & Use Cases

  • Topology and version guidance with sensible defaults (multi-node for production, single-node for dev/test).
  • Preflight-driven provisioning that validates storage, addon readiness, and network requirements.
  • Clear guidance for next-hop routing to capability layers and observability when the cluster is created.

Quick Start

Draft and apply a minimal Elasticsearch cluster manifest using the default multi-node topology and run kubeblocks-preflight first to verify readiness.

Frequently Asked Questions about kubeblocks-engine-elasticsearch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Elasticsearch on Kubernetes using KubeBlocks?

Deploy Elasticsearch on KubeBlocks using a guided create-time path that selects topology, version, and storage. This provisioning process applies to development, staging, and production scenarios, handling cluster sizing and network connections.

What is the preflight workflow for provisioning Elasticsearch on KubeBlocks?

The preflight workflow validates storage, addon readiness, and network requirements before provisioning Elasticsearch on KubeBlocks. It enforces a preflight-first approach to ensure environment readiness and reduce deployment guesswork.

Can I use a single-node Elasticsearch topology for development on KubeBlocks?

Yes, KubeBlocks provides topology guidance with sensible defaults, offering a single-node topology for development and test environments. It uses multi-node topology as the default for production provisioning scenarios to ensure reliability.

Does the KubeBlocks Elasticsearch engine support legacy addon paths?

Yes, the KubeBlocks Elasticsearch engine preserves the legacy addon-elasticsearch path for compatibility. It uses the engine-create-matrix as the source of truth for topology and sizing while maintaining backward compatibility with older workflows.

What should I do after creating an Elasticsearch cluster on KubeBlocks?

After creating an Elasticsearch cluster on KubeBlocks, follow the provided guidance for next-hop routing to capability layers and observability. This ensures your newly provisioned cluster is properly integrated into your broader infrastructure.