Meshery v0.8.0 Roadmap

This post includes the proposed roadmap for Meshery v0.8.0 release. Use this thread to refine and hardened these plans and assignments. If you are interested in contributing to or leading any of these items, please comment below.


Theme or Meshery Component
:meshery: [@Theme Champion]
[?] = help wanted
:x: incomplete/no implementation
:warning: partial implementation
:white_check_mark: done


  1. See v0.8.0 Milestone in meshery/meshery.
  2. See the Meshery Architecture deck for additional visual designs and functional specifications.

Lifecycle Management

  • Support AWS and GCP (spec) [@MUzairS15]

    • Static Model Generation sources AWS, GCP as K8s CRDs. [@MUzairS15]
    • Relationships, Connections, Credentials for AWS, GCP
    • CLI: Refactor system config for AKS (spec) [?]
    • CLI: Refactor system config for EKS (spec) [@hexxdump]
  • GitOps: Expand Flux Integration with Helm Repo [?]

  • MeshSync: Configurable and Tiered Discovery [:meshery:@Daniel.Kiptoon]
    • Support for runtime registration of new fingerprints. [@MUzairS15]
    • Support for composite fingerprints where keys span multiple entities (or not just the entity being discovered). [?]
Roadmap v0.9.0 (stretch goal)
  • CLI: Meshconfig: Support for multi-cluster (spec) [?]

Registry & Models [:meshery:@MUzairS15]


  • Refactor Model as first-class resource. [?]
    • Model import/export [?]
  • Server: Model Generator for direct Helm Chart or K8s Manifest Retrieval
    • Dynamic Generation via URL (Chart, Manifest) upon Design import. [?]
  • Support for Sub-Categories [?]


  • Refactor Relationship as first-class resource. [?]
    • Relationship Coverage for All K8s Components (spec) [@Lee][@Ripul.Handoo]
    • Evaluation: Enhancing the mechanism used to reference policies on disk or in registry. [?]
    • Classification of Policy Evaluation into client-side, server-side, and cluster-side moments of evaluation and their distinctions. [@Lee]
    • SelectorSets for Relationships [@MUzairS15]

Registry [:meshery:@Yash.Sharma]

  • UI: (Capabilities) Registry [:meshery:@Yash.Sharma] :warning:
  • Registration of connections and credentials [?]
  • CLI: Support for commands: models, relationships, components, connections, credentials [@alphaX86]

Spaces [:meshery:@theBeginner86]

Adapters & Performance Management [:meshery:@Xin_Huang]

  1. Adapter: Evolve meshes.proto to adapters.proto
  2. :nighthawk: Externalize Nighthawk (spec) [@Lee][@Xin_Huang][@MUzairS15]
    1. :nighthawk: Nighthawk as a Meshery Adapter (meshery-nighthawk) [@Xin_Huang]
    2. :nighthawk: Server: Lifecycle Management of meshery-nighthawk in Meshery Server [@MUzairS15]
    3. :nighthawk: CLI: mesheryctl perf support for load generator / adapter selection [?]
    4. :nighthawk: UI: meshery-nighthawk adapter chip [@Yash.Sharma]

Basic Adaptive Load Controller

Roadmap v0.9.0 (stretch goal)

Basic Adaptive Load Controller (spec) (v0.9.0)

  • Exposure of “Adaptive Test” in Meshery UI. [?]
  • Meshery Server endpoints. [@Xin_Huang]
  • Storage of n result sets in Provider for a given Performance Profile. [@Xin_Huang], [@theBeginner86]

Custom Telemetry Provider

Roadmap v0.9.0 (stretch goal)
  • Multiple Telemetry Providers and Custom Boards (spec) [?]
  • User-defined Dashboards and Metrics (spec) [?]

Open Container Image (OCI) Support [:meshery:@theBeginner86]

  • Adopt OCI as the packaging and distribution format for Meshery Designs, Patterns, Filters, Models (#6447) (Design Spec)
  • CLI: Pushing and pulling Models and Designs from OCI registries [?] (Design Spec)
Roadmap v0.9.0 (stretch goal)
  • Connection: Supporting OCI Registries (#8855) (Design Spec)
  • Signing OCI exported images (#8855)
  • Export a Design to GitHub [?]
  • Export a Model to Docker Hub [?]

Extensibility [?]

  • UI: Extensible Authorization [@Yash.Sharma]
  • Expand Meshery’s Integration with Artifact Hub #9966
    • [Artifact Hub] Meshery Designs as a new Artifact Hub kind #9967

Docs [:meshery: @iArchitSharma]

  • [Playground] Learning Paths: Cloud Native tutorials with Meshery Playground #9832
    • Creating three tutorials per category, allowing learners to perform hands-on lab interactively in the live cluster environment in Meshery Playground. [@sandramsc]
  • Automated publication of security key reference [@Yash.Sharma]
  • Automated publication of Model Relationships and Components [@theBeginner86][@vishalvivekm]
  • Dynamic Menu: Sidebar Table of Contents [@iArchitSharma]

UI [:meshery: @Antonette.Caldwell]

  • UI: Complete incorporation of RTK [@Sudhanshu_Dasgupta]
    • UI: Complete elimination of useEffect.
  • UI: All components sourced from Sistent [@Senali]
    • UI: Switch to Sistent as the theme provider.
  • UI: Sistent Design System
  • UI: Support for Material UI v5 [?]

CLI [:meshery: @alphaX86 @hexxdump]

  • CLI: code coverage goal: 50% [?]
  • :warning: CLI: Full migration from Apps to Designs [@theBeginner86]
Roadmap v0.9.0 (stretch goal)
  • CLI: system report - diagnostics reporting (stretch goal) [?]

Server [:meshery: @MUzairS15]

  • Server: code coverage goal: 25% [?]

Meshery Catalog [:meshery: @vishalvivekm]

  • 100% design-type coverage
  • 50% technology-type coverage

See the Meshery Architecture deck for additional visual designs and functional specifications.


I would like to champion this MeshSync feature


I’m willing to lead this one :slight_smile:


Willing to lead this one


Maybe we can have the present design as a new feature in the playground like present slide in Google Slides.


Docs (

  • Automated provisioning of the keys
  • New Shortcodes

Meshery is an awesome tool for learning cloud and cloud-native technologies, and so leading the creation of tutorials/hands-on labs is something I want to pursue.

Willing to contribute to models.

Dropping this here as a start then we can flesh it further

1 Like

I want to work on UI. Current work includes

UI: Complete incorporation of RTK [@Sudhanshu_Dasgupta]
- UI: Complete elimination of useEffect.

Hey @abhishekmmgn thanks for raising your hand, please checkout this issue #9985 for more info

Oh, okay. Thanks for the help