Skip to content

Control Plane Components

This page lists the various components in the control plane of the service mesh along with their locations, descriptions, and default resource settings.

Component Name Location Description Default Resource Settings
mspider-ui Global Management Cluster Service Mesh Interface
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
mspider-ckube Global Management Cluster Accelerator component for Kubernetes API Server, used to call resources related to the global cluster
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
mspider-ckube-remote Global Management Cluster Used to call remote Kubernetes clusters, aggregate multi-cluster resources, and accelerate
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
mspider-gsc-controller Global Management Cluster Service mesh management component for mesh creation, mesh configuration, and mesh control plane lifecycle management, as well as permissions management and other Mspider control plane capabilities
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
mspider-api-service Global Management Cluster Provides interfaces for Mspider backend API interactions and control behaviors
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
Hosted Mesh
istiod-{meshID}-hosted Control Plane Cluster Used for hosted mesh policy management
  • requests: CPU: 100m; Memory: 100m
  • limits: CPU: Not set; Memory: Not set
mspider-mcpc-ckube-remote Control Plane Cluster Call remote mesh working clusters, accelerate, and aggregate multi-cluster resources
  • requests: CPU: 100m; Memory: 50m
  • limits: CPU: 500m; Memory: 500m
mspider-mcpc-mcpc-controller Control Plane Cluster Aggregate multi-cluster data plane information
  • requests: CPU: 100m; Memory: 0
  • limits: CPU: 300m; Memory: 1.56G
{meshID}-hosted-apiserver Control Plane Cluster Hosted control plane virtual cluster API Server
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
{meshID}-etcd Control Plane Cluster Hosted control plane virtual cluster etcd, used for hosted mesh policy storage
  • requests: CPU: Not set; Memory: Not set
  • limits: CPU: Not set; Memory: Not set
istiod Working Cluster Mainly used for sidecar lifecycle management in the local cluster
  • requests: CPU: 100; Memory: 100
  • limits: CPU: Not set; Memory: Not set
Private Mesh
istiod Used for policy creation, deployment, and sidecar lifecycle management work
  • requests: CPU: 100; Memory: 100
  • limits: CPU: Not set; Memory: Not set
mspider-mcpc-ckube-remote Working Cluster Call remote mesh working clusters
  • requests: CPU: 100m; Memory: 50m
  • limits: CPU: 500m; Memory: 500m
mspider-mcpc-mcpc-controller Working Cluster Collect cluster data plane information
  • requests: CPU: 100m; Memory: 0
  • limits: CPU: 300m; Memory: 1.56G
External Mesh
mspider-mcpc-ckube-remote Working Cluster Call remote mesh working clusters
  • requests: CPU: 100m; Memory: 50m
  • limits: CPU: 500m; Memory: 500m
mspider-mcpc-mcpc-controller Working Cluster Collect cluster data plane information
  • requests: CPU: 100m; Memory: 0
  • limits: CPU: 300m; Memory: 1.56G

These are the default resource settings for each control plane component of the service mesh. You can customize CPU and memory resources for each workload in the Container Management module.

Comments