Generate v1beta1 compatible Components

[leecalcote]

Current Behavior

On boot, Meshery Adapters connect to Meshery Server and register their model(s), which contain any number of components.

The current collection of components within the model of this adapter are antiquated and incompatible with the latest version of Meshery.

Desired Behavior

They need to be brought inline with the v1beta1 schemas for models and components (and v1alpha3 for relationships).

Implementation

Reuse the same meshkit functionality that is already used by Meshery Server and Meshery CLI. See arch slides 44 and 45?

To do so, you shouldn’t need to change the gRPC protobuf, but if that becomes necessary, the proto needs an overhaul to be made much more generic in nature - by the way in which it describes operations. It also needs to be renamed and should not use the term “meshes”.

Note: be aware of the functionality contained within the Meshery adapter library.

Acceptance Tests

• The adapter successfully registers its model(s) with Meshery Server.
• Designs that contain components from that have been registered by an adapter are sent to the adapter upon deployment of that design.

Mockups

---

Contributor Guides and Resources

• 📝 Meshery Adapters Spreadsheet
• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack