kubeblocks-addon-mongodb

Migrate legacy MongoDB provisioning references on KubeBlocks by pointing existing deployments to the primary entry kubeblocks-engine-mongodb. This skill provides a read-only reference path and detailed guidance to safely transition deprecated addon configurations to the primary engine.

The legacy MongoDB addon path serves as a backward-compatible reference for Kubernetes deployments that still rely on deprecated provisioning configurations. It enforces read-only workflows to prevent runtime confusion while guiding teams toward the primary kubeblocks-engine-mongodb entry point.

You can keep kubeblocks-addon-mongodb callable for older references, but it is not recommended for cold-start provisioning. The primary create-time entry is kubeblocks-engine-mongodb, making this legacy path strictly a migration and compatibility shim.

Your KubeBlocks MongoDB deployment references a deprecated addon because existing configurations were created before the primary engine migration. This skill intercepts those legacy references, providing a safe, read-only workflow to prevent runtime errors and guide the transition.

The best way to handle deprecated MongoDB addon references in KubeBlocks is to use this compatibility shim as a temporary bridge. It provides documentation and a clear migration path to update your workflows to the primary kubeblocks-engine-mongodb engine.