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

kubeblocks-addon-milvus

Route legacy Milvus provisioning requests to kubeblocks-engine-milvus on KubeBlocks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility shim to preserve Milvus provisioning workflows on KubeBlocks for older references, ensuring users can continue using non-main entry points without breaking deployments.

Core Features & Use Cases

  • Backward compatibility: routes legacy Milvus provisioning requests to the primary engine path.
  • Reference stability: maintains documented workflows while upgrades occur.
  • Operational clarity: prevents drift between old and new Milvus addon entry points during transitions.

Quick Start

Route legacy Milvus provisioning calls through this shim to kubeblocks-engine-milvus.

Frequently Asked Questions about kubeblocks-addon-milvus

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

FAQPage Schema
How do I keep Milvus provisioning working after upgrading KubeBlocks?▼

A legacy compatibility shim routes Milvus provisioning requests to the primary kubeblocks-engine-milvus path, maintaining backward compatibility without requiring workflow changes.

What is a legacy shim for Milvus addon provisioning?▼

A legacy shim preserves older Milvus provisioning workflows on KubeBlocks by routing requests to the main engine entry, preventing drift between old and new addon references during system transitions.

Do I need to change my code to migrate to the main Milvus engine entry?▼

No, you do not need to change your code. The shim intercepts legacy provisioning calls and automatically routes them to kubeblocks-engine-milvus, ensuring documented workflows remain stable.

Can I use the legacy kubeblocks-addon-milvus path without breaking deployments?▼

Yes, you can continue using the legacy kubeblocks-addon-milvus path safely. The shim ensures operational clarity by preventing drift between old and new Milvus addon entry points during migrations.

When should I use a compatibility shim for Milvus provisioning?▼

Use a compatibility shim for Milvus provisioning when your environment still calls the legacy addon path and you need to migrate to the main engine entry without breaking existing deployments.

Related Skills

Explore More Software Engineering Skills→
apecloudapecloud
3

kubeblocks-addon-kafka

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

Official
Intermediate
apecloudapecloud
3

kubeblocks-engine-milvus

Provision Milvus on KubeBlocks with topology, version, storage, and connection settings.

Official
Advanced
apecloudapecloud
3

kubeblocks-addon-mongodb

Provide a legacy MongoDB provisioning reference for migration to kubeblocks-engine-mongodb.

Official
Intermediate
apecloudapecloud
3

kubeblocks-addon-rabbitmq

Provides legacy RabbitMQ provisioning compatibility shim for KubeBlocks.

Official
Basic