Platform vs Cluster

In Kublr, you can select what to create: Plaform or Cluster. Both are actually Kubernetes clusters, but with the different set of features (Platform has more), so Kublr provides different user interfaces for comfortable installing and editing of these features.

Installation Types

Basic Features

The table below shows what you can do via Kublr user interface in case of Plaform or Cluster:

Note that both interfaces are only intended for your convinience, not for limitation - you can add or remove ANY feature via CUSTOMIZE SPECIFICATION - during installation or later editing.

FEATUREPlatformCluster
Included by default?May be included?May be excluded?Included by default?May be included?May be excluded?
Ingress Controller »YesNANoNoYesYes
» NGINX Ingress ControllerYesNANoNoYesYes
» Let’s EncryptNoYesYesNoYesYes
Control PlaneYesNANoNoNoNA
Centralized Logging/Self-Hosted Logging (a) »YesYesYesNoYesYes
» FluentdYesWPWPNoWPWP
» ElasticsearchYesWPWPNoWPWP
» KibanaYesWPWPNoWPWP
Centralized Monitoring/Self-Hosted Monitoring (a) »YesYesYesNoYesYes
» PrometheusYesNAWPNoWPWP
» GrafanaYesYesYesNoYesYes
» Alert ManagerYesNoYesNoYesYes

Table annotation:

  • NA = not applicable
  • WP = with parent feature only
  • (a) Double names mean different names of a feature for platform and cluster. If this is the case then format is “Name for Platform/Name for Cluster”.

Provider Specific Features

AWS

FEATUREPlatformCluster
Included by default?May be included?May be excluded?Included by default?May be included?May be excluded?
Centralized Logging/Self-Hosted Logging »YesYesYesNoYesYes
» AWS CloudWatch LogsNoYesYesNoWPYes