Introduction to Pluggable Components

Edit

Introduction

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.

Enable Pluggable Components

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.

Pluggable Components

Pluggable Components Configuration Table

Attention: For multi-node installation, there should be at least ONE node 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.

ComponentFeatureCPUMemory
openpitrix-systemApplication Store0.3 core300 MiB
kubesphere-alerting-systemalerting and notification system0.08 core80 M
kubesphere-devops-system(All-in-one)DevOps System34 m2.69 G
kubesphere-devops-system(Multi-node)DevOps System0.47 core8.6 G
istio-systemIstio-based Service Mesh System2 core3.6 G
kubesphere-logging-systemlogging system56 m2.76 G
metrics-serverenable HPA and “kubectl top”5 m44.35 MiB
GitLab + HarborSource code repository & Image registry (3rd party App)0.58 core3.57 G

Components Version

The components marked with * are required in minimal installation. Others are pluggable components.

ComponentVersion
KubeSphere2.1.1
Kubernetesv1.16.7
etcd3.2.18
Prometheusv2.5.0
Fluent Bitv1.3.5
Elasticsearchv6.7.0 ( Support using external ElasticSearch 7.x )
Istiov1.3.3
OpenPitrix (App Store)v0.4.8
Jenkinsv2.176.2
SonarQubev7.4-community
GitLab11.8.1
Harbor1.7.5