Understanding Meshery Relationships
Meshery uses relationships to map how interconnected components interact.
Working with Components
Meshery Designs are descriptive, declarative characterizations of how your Kubernetes infrastructure should be configured.
Categories:
Designs
Designs are declarative, descriptive characterizations of how your Kubernetes infrastructure should be configured. Designs are versioned and can be shared with other users and teams. Designs are the primary tool for collaborative authorship of your infrastructure and services.
Using Designs
Design Relationships and Restrictions
- Access to Designs may be granted to one or more users.
Controlling Access to Designs
When creating a new design, by default its visibility will be set to public unless you are an active Layer5 Cloud subscriber, in which case you can change this default to private.
Google Docs Analogy
Google Docs are a useful analogy for understanding Meshery designs. In many ways a Meshery design is like a single Google Doc in that they are collaboratively authored, versioned, permissioned and can move from workspace to workspace. Workspaces, a shared collection of designs, can be likened to a Google Drive, a shared collection of files.Recent Discussions on Kanvas
- Oct 14 | Explore Meshery's Published Relationship Design Examples by Awani Alero
- Oct 03 | Design Review RFC: Kanvas Empty State Enhancement by Lee Calcote
- Jul 19 | [For Discussion] Visual indication of semantically vs non-semantically meaningful Meshery components by Lee Calcote
- Jun 07 | What are the conditions for a "System is unhealthy" warning? by James
- May 30 | Looking for a meshmate to help with first PR by Faisal Imtiyaz123
- Feb 28 | For Discussion: Capturing potential, but unrealized Relationships in Design Snapshots by Lee Calcote
- Feb 12 | Hint on Scaling & Verifying Cronjob in Playground by Sandra Ashipala
- Sep 28 | Trying to add screenshots of Containerd & Curiefense integration by Raman Thakur