Concepts

Concepts for understanding Meshery’s various features and components.

Concepts

Logical

  • Components - Meshery Components identify and characterize infrastructure under management.
  • Connections - Meshery Connections are managed and unmanaged resources that either through discovery or manual entry are managed by a state machine and used within one or more Environments.
  • Credentials - Meshery uses one or more Credentials when authenticating to a managed or unmanaged Connection.
  • Designs - Meshery Designs are descriptive, declarative characterizations of how your Kubernetes infrastructure should be configured.
  • Environments - Environments are how you organize your deployment targets (whether on-premises servers or cloud services) into resource groups.
  • Models - Meshery uses a set of resource models to define concrete boundaries to ensure extensible and sustainable management.
  • Patterns - Meshery Patterns are descriptive, declarative characterizations of how your Kubernetes infrastructure should be configured.
  • Policies - Meshery Policies enable you with a broad set of controls and governance of the behavior of systems under Meshery's management.
  • Registry - Meshery Registry is a database acting as the central repository for all capabilities known to Meshery. These capabilities encompass various entities, including models, components, relationships, and policies.
  • Relationships - Meshery Relationships identify and facilitate genealogy between Components.
  • Workspaces - Meshery Workspaces act as central collaboration point for teams.

Architectural

  • Adapters - Adapters extend Meshery's management capabilities in any number of ways, including lifecycle, configuration, performance, governance, identity...
  • Architecture - overview of different individual components of Meshery architecture and how they interact as a system.
  • Broker - Meshery broker component facilitates data streaming between kubernetes cluster components and outside world.
  • Catalog - Browsing and using cloud native patterns
  • Database - Meshery offers support for internal caching with the help of file databases. This has been implemented with several libraries that supports different kinds of data formats.
  • MeshSync - MeshSync ensures Meshery Server is continuously in-sync with the state of infrastructure under management.
  • Operator - Meshery Operator controls and manages the lifecycle of components deployed inside a kubernetes cluster