Meshery Operator is a Kubernetes Operator that deploys and manages the lifecycle of two Meshery components critical to Meshery’s operations of Kubernetes clusters. Deploy one Meshery Operator per Kubernetes cluster under management - whether Meshery Server is deploy inside or outside of the clusters under management.
It is recommended to deploy one Meshery Operator per cluster.
Controllers managed by Meshery Operator
Meshery broker is one of the core components of the meshery architecture. This controller manages the lifecycle of broker that meshery uses for data streaming across the cluster and the outside world.
See Meshery Broker for more information.
MeshSync Controller manages the lifecycle of MeshSync that is deployed for resource synchronization for the cluster.
See MeshSync for more information.
When is Meshery Operator deployed and when is it deleted?
As a Kubernetes custom controller, Meshery Operator is provisioned and deprovisioned when Meshery Server is connected to or disconnected from Kubernetes cluster. Meshery Server connections to Kubernetes clusters are controlled using Meshery Server clients:
mesheryctl or Meshery UI. This behavior described below is consistent whether your Meshery deployment is using Docker or Kubernetes as the platform to host the Meshery deployment.
mesheryctl initiates connection to Kubernetes cluster when
mesheryctl system start is executed and disconnects when
mesheryctl system stop is executed. This behavior is consistent whether your Meshery deployment is using Docker or Kubernetes as the platform to host the Meshery deployment.
Meshery UI Meshery UI offers more granular control over the deployment of Meshery Operator in that you can remove Meshery Operator from a Kubernetes cluster without disconnecting Meshery Server from the Kubernetes cluster. You can control the deployment of Meshery Operator using the on/off switch found in the Meshery Operator section of Settings.
Does the Meshery Operator use an SDK or framework?
Yes, Meshery Operator used the Operator SDK.