Ensuring Extension Compatibility with Meshery

The Meshery ecosystem is designed for extensibility, with the core platform (meshery/meshery) providing extension points for a variety of plugins, collectively managed in the meshery-extensions GitHub organization. To ensure a stable and seamless user experience, it is critical that extensions remain compatible with the Meshery platform, especially when shared frameworks or dependencies are updated.

This guide outlines the key areas of compatibility and provides a general process for extension developers to follow when Meshery’s underlying frameworks are updated.

Meshery's Bill of Materials

Meshery’s version is defined by its Bill of Materials (BOM), which specifies versions for Go, Node.js, and other key dependencies. Extension developers should reference the BOM to ensure alignment.

Key Areas for Compatibility

Compatibility between Meshery and its extensions spans several areas. When the Meshery platform is updated, one or more of the following are likely to change:

1. Language Runtimes : Meshery and its extensions are often built using the same programming languages. Ensuring version alignment is the first step to compatibility.

2. Shared Go Libraries : Meshery and its extensions share a common set of libraries (meshery/meshkit) that provide foundational utilities, API clients, and data models.

3. UI Frameworks and Component Libraries : UI-based extensions must align with Meshery’s frontend technology stack to ensure a consistent user experience and functional correctness.

4. Build and CI/CD Tooling : The build process for extensions should be compatible with the environment and tooling used by Meshery.

General Process for Verifying Compatibility

When Meshery’s Bill of Materials is updated, follow this general process to verify and update your extension.

1. Identify the Changes in Meshery

Start by reviewing the release notes or commit history of the meshery/meshery repository to understand what has changed. Pay close attention to:

• Go version updates in the root go.mod and install/Makefile.core.mk.
• Version changes for meshery/meshkit and other key dependencies in go.mod.
• Updates to UI framework versions in ui/package.json.
• Changes to .proto files for gRPC services.

2. Update Your Extension’s Dependencies

In your extension’s repository, update your dependency files to match the versions used in Meshery.

• For Go-based extensions :
  1. Update the go directive in your go.mod file to match Meshery’s.
  2. Update the required version of github.com/meshery/meshkit and other shared modules:

go get github.com/meshery/[email protected]
go mod tidy

• For UI-based extensions :
  1. Update the versions of React, Next.js, MUI, and other relevant packages in your package.json.
  2. Run npm install or yarn install to update your dependencies.

3. Rebuild and Test Your Extension

After updating the dependencies, rebuild your extension to ensure it compiles without errors.

• For Go-based extensions :

go build -o <your-extension-binary>

• For UI-based extensions :

npm run build

4. Perform Integration Testing

Run your updated extension with the latest version of Meshery to verify end-to-end compatibility.

1. Run the latest Meshery server. Ensure you are using the build corresponding to the dependency updates.
2. Run your updated extension.
3. Monitor the logs of both Meshery and your extension for any runtime errors, panics, or warnings related to version mismatches.
4. Thoroughly test your extension’s functionality. Verify that all interactions with Meshery are working as expected, including API calls and UI integrations.

By following this process, you can ensure that your extension remains compatible with the ever-evolving Meshery platform, providing a reliable and consistent experience for all users.

[ Previous

Providers ](/v0.9/extensibility/providers)[ Next

UI Plugins ](/v0.9/extensibility/ui)