Meshery

Meshery's high project velocity necessitates a revision in its governance and organizational structure to align with the scale of its growing complexity and community contributions. To best serve its expansive ecosystem, Meshery maintainers have opted to partition its numerous GitHub repositories into two distinct organizations: github.com/meshery for the core platform and meshery-extensions for extensions and integrations.

Meshery Extensions are plugins or add-ons that enhance the functionality of the Meshery platform beyond its core capabilities. Meshery supports different types of extensions):

• Academies: Academy extensions enable Meshery as an integrated learning platform.
• Adapters: Adapters allow Meshery to interface with the different cloud native infrastructure.\
• Build-time: enable integrators to inject custom configurations, data, provider extensions, and other resources directly into the Meshery container image at build-time.
• CLI: Helm and kubectl plugins that let you create Kanvas snapshots from Helm charts, Kubernetes manifests, and the current state of your Kubernetes cluster, then upload them to Meshery.
  • Kubectl CLI Plugin
  • Helm CLI Plugin
• Load Generators: for performance characterization and benchmarking.
• Models: component-based (semantically and non-semantically meaningful) support for a broad variety of platforms, tools, and technologies.
• Providers: for connecting to different cloud providers and infrastructure platforms.
• Schemas - Meshery schemas are conscientiously extensible via x-* vendor extensions.
• UI Plugins: Meshery UI has a number of extension points that allow users to customize their experience with third-party plugins.

This organization is managed by Meshery core and extension maintainers. Repositories in this organization need to be sponsored and created by one or more of the core maintainers. Read more about the rationale for the project's multi-organization approach and it's governance structure.

See Meshery and it's plugins in-action