skills.rest
apecloud
apecloudOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kubeblocks-addon-elasticsearch

Route legacy Elasticsearch provisioning references to kubeblocks-engine-elasticsearch on KubeBlocks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backward compatibility shim for Elasticsearch provisioning on KubeBlocks, preserving older workflows and references while pointing users to the primary engine when possible.

Core Features & Use Cases

  • Maintains legacy entrypoints and routing to kubeblocks-engine-elasticsearch
  • Documents behavior and deprecations to ease migration
  • Supports both single-node dev/test and multi-node production workflows

Quick Start

Use this shim to reference Elasticsearch provisioning workflows when the primary entry is kubeblocks-engine-elasticsearch.

Frequently Asked Questions about kubeblocks-addon-elasticsearch

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

FAQPage Schema
How do I keep legacy Elasticsearch provisioning scripts working on KubeBlocks?▼

This compatibility shim preserves legacy Elasticsearch provisioning entry points on KubeBlocks by routing older create-time references to the primary kubeblocks-engine-elasticsearch engine, ensuring existing scripts continue to function.

What is backward compatibility for Elasticsearch provisioning on KubeBlocks?▼

Backward compatibility for Elasticsearch provisioning on KubeBlocks means maintaining legacy entry points and routing them to the primary engine, ensuring older workflows and scripts continue to work without modification.

Can I use this Elasticsearch provisioning shim for multi-node production workflows?▼

Yes, the Elasticsearch provisioning shim supports both single-node dev/test environments and multi-node production workflows on KubeBlocks while routing to the primary engine.

When should I migrate from legacy Elasticsearch provisioning to the primary engine?▼

You should migrate from legacy Elasticsearch provisioning to the primary kubeblocks-engine-elasticsearch engine for ongoing usage, as this shim only provides a stable fallback and documents deprecations to ease migration.

Why does my KubeBlocks Elasticsearch script reference a deprecated provisioning entry point?▼

Your KubeBlocks Elasticsearch script references a deprecated provisioning entry point because this shim preserves legacy create-time references, routing them to the primary engine while documenting behavior for migration.

Related Skills

Explore More Software Engineering Skills→
apecloudapecloud
3

kubeblocks-addon-redis

Route legacy Redis provisioning requests to a compatibility shim in KubeBlocks.

Official
Basic
apecloudapecloud
3

kubeblocks-addon-rabbitmq

Provides legacy RabbitMQ provisioning compatibility shim for KubeBlocks.

Official
Basic
apecloudapecloud
3

kubeblocks-engine-elasticsearch

Provision Elasticsearch on KubeBlocks with preflight validation and topology selection.

Official
Advanced
apecloudapecloud
3

kubeblocks-addon-kafka

Route legacy Kafka provisioning requests to kubeblocks-engine-kafka.

Official
Intermediate