generated from layer5io/layer5-repo-template
-
Notifications
You must be signed in to change notification settings - Fork 82
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Victoria Nduka <[email protected]>
- Loading branch information
Showing
1 changed file
with
32 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,32 @@ | ||
Relationships define the nature of interaction between interconnected components in Meshery. They represent various types of connections and dependencies between components no matter the genealogy of the relationship such as parent, siblings, binding. Relationships have selectors, metadata, and optional parameters. | ||
--- | ||
title: Understanding Meshery Relationships | ||
weight: 4 | ||
type: docs | ||
description: > | ||
Meshery uses relationships to map how interconnected components interact. | ||
categories: [Designer] | ||
tags: [designs, relationships, components] | ||
--- | ||
|
||
## What are Meshery Relationships? | ||
Relationships define the nature of interaction between interconnected components in Meshery. They represent various types of connections and dependencies between components no matter the genealogy of the relationship such as parent, siblings, binding. | ||
|
||
## Types of Relationships | ||
|
||
Relationships are categorized into different kinds, types, and subtypes, so that can be expressive of the specific manner in which one or more components relate to one another. | ||
|
||
Here is a list of the different types of relationships that Meshery supports: | ||
|
||
1. Edge-Network | ||
The Edge-Network rlationship type configures the networking between one or more components. An example is the relationship between a Ingress and a Deployment | ||
(insert image) | ||
1. Edge-Firewall | ||
(insert image) | ||
1. Edge-Mount | ||
(insert image) | ||
1. Edge-Permission | ||
(insert image) | ||
1. Hierarchical-Inventory | ||
(insert image) | ||
1. Hierarchical-Parent | ||
(insert image) |