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 started with a minimal installation if you do not enable them.
KubeSphere has six pluggable components as the following listed. You can enable any of them according to your demands. It is highly recommended that you install these pluggable components to discover the full-stack features and capabilities provided by KubeSphere. Please ensure your machines have sufficient CPU and memory before enabling them.
Attention: For multi-node installation, there should be at least
ONEnode having more than 8G of available memory, which is used for dependencies cache in CI node.
The following table shows the name, description and rough CPU/memory requirements of each component.
|openpitrix-system||Application Store||0.3 core||300 MiB|
|kubesphere-alerting-system||alerting and notification system||0.08 core||80 M|
|kubesphere-devops-system（All-in-one）||DevOps System||34 m||2.69 G|
|kubesphere-devops-system（Multi-node）||DevOps System||0.47 core||8.6 G|
|istio-system||Istio-based Service Mesh System||2 core||3.6 G|
|kubesphere-logging-system||logging system||56 m||2.76 G|
|metrics-server||enable HPA and "kubectl top"||5 m||44.35 MiB|
|GitLab + Harbor||Source code repository & Image registry (3rd party App)||0.58 core||3.57 G|
The components marked with
* are required in minimal installation. Others are pluggable components.
|Elasticsearch||v6.7.0 ( Support using external ElasticSearch 7.x )|
|OpenPitrix (App Store)||v0.4.8|