< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />

Enable Pluggable Components โ€” Overview

KubeSphere has decoupled some core feature components since v2.1.0. These components are designed to be pluggable which means you can enable them either before or after installation. By default, KubeSphere will be deployed with a minimal installation if you do not enable them.

Different pluggable components are deployed in different namespaces. You can enable any of them based on your needs. It is highly recommended that you install these pluggable components to discover the full-stack features and capabilities provided by KubeSphere.

For more information about how to enable each component, see respective tutorials in this chapter.

Resource Requirements

Before you enable pluggable components, make sure you have enough resources in your environment based on the tables below. Otherwise, components may crash due to a lack of resources.


The following request and limit of CPU and memory resources are required by a single replica.

KubeSphere App Store

CPU Request0.3 core
CPU LimitNone
Memory Request300 MiB
Memory LimitNone
NotesProvide an App Store with application lifecycle management. The installation is recommended.

KubeSphere DevOps System

PatternAll-in-One installationMulti-node installation
CPU Request34 m0.47 core
CPU LimitNoneNone
Memory Request2.69 G8.6 G
Memory LimitNoneNone
NotesProvide one-stop DevOps solutions with Jenkins pipelines and B2I & S2I.The memory of one of the nodes must be larger than 8 G.

KubeSphere Monitoring System

Sub-component2 x Prometheus3 x AlertmanagerNotification Manager
CPU Request100 m10 m100 m
CPU Limit4 coresNone500 m
Memory Request400 MiB30 MiB20 MiB
Memory Limit8 GiBNone1 GiB
NotesThe memory consumption of Prometheus depends on the cluster size. 8 GiB is sufficient for a cluster with 200 nodes/16,000 Pods.--


The KubeSphere monitoring system is not a pluggable component. It is installed by default. The resource request and limit of it are also listed on this page for your reference as it is closely related to other components such as logging.

KubeSphere Logging System

Sub-component3 x Elasticsearchfluent bitkube-eventskube-auditing
CPU Request50 m20 m90 m20 m
CPU Limit1 core200 m900 m200 m
Memory Request2 G50 MiB120 MiB50 MiB
Memory LimitNone100 MiB1200 MiB100 MiB
NotesAn optional component for log data storage. The internal Elasticsearch is not recommended for the production environment.The log collection agent. It is a required component after you enable logging.Collecting, filtering, exporting and alerting of Kubernetes events.Collecting, filtering and alerting of Kubernetes and KubeSphere auditing logs.

KubeSphere Alerting and Notification

CPU Request0.08 core
CPU LimitNone
Memory Request80 M
Memory LimitNone
NotesAlerting and Notification need to be enabled at the same time.

KubeSphere Service Mesh

CPU Request1 core
CPU LimitNone
Memory Request3.5 G
Memory LimitNone
NotesSupport grayscale release strategies, traffic topology, traffic management and distributed tracing.

Receive the latest news, articles and updates from KubeSphere

Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.