Cluster & Platform Features

Below you can find descriptions for the features you can optionally add to your clusters and platforms.

Features

To access the features information, in your cluster or platform dialog, click the Features tab at the top of the dialog.

Logging

Applicable for:
ProviderAWS, Azure, GCP, VMware vSphere, On-Premises
TypeCluster, Platform

Refer to the detailed overview in the Logging article.

For Cluster

Application and system logs can help you understand what is happening in your clusters. The logs are particularly useful for troubleshooting and monitoring cluster activity.

The Self-hosted ElasticSearch/Kibana can be used when you need dedicated Logging in the cluster.

Select the Self-Hosted Logging option for log records to be transferred both into Centralized and Self-hosted ElasticSearch.

When selected, you can additionally specify:

For Elasticsearch:

  • Number of Master nodes for ElasticSearch cluster. Note that the number of maste nodes should be 1, 3 or more. You can find more details here.
  • Number of Data nodes that hold data and perform data related operations such as CRUD, search, and aggregations.
  • Number of Client nodes that follow client requests.

The Persistence enabled option is selected by default.

Features-Logging

Optionally, you can also specify the Data node disk size in GB. Note that a 4 GB storage will be additionally created for each master node.

For Platform

Unlike cluster:

  • Logging cannot be disabled.
  • It has name Centralized Logging.
  • For AWS, it has an Add AWS CloudWatch Logs option.

Monitoring

Applicable for:
ProviderAWS, Azure, GCP, VMware vSphere, On-Premises
TypeCluster, Platform

Refer to the detailed overview in the Monitoring article.

For Cluster

Kublr collects metrics including detailed resource usage information on the managed clusters and in the platform at all operation levels. In addition to the centralized monitoring subsystem, it is possible to deploy self-hosted monitoring stack in each managed cluster.

Select Self-hosted Monitoring and specify components that need to be installed and their configuration:

  • Prometheus and
  • Grafana and/or
  • AlertManager

Persistance can be enabled or discabled for each componets and the Disk size can be specified.

Features-Monitoring

For Platform

Unlike cluster:

  • Neither Prometheus nor Grafana monitoring can be disabled.
  • It has name Centralized Monitoring.
  • You can only enable or disable persistence for each option.

Ingress Controller

Applicable for:
ProviderAWS, Azure, GCP, VMware vSphere, On-Premises
TypeCluster, Platform

Currently, Kublr supports nginx ingress controller and Let’s Encrypt for automatic HTTPS certificate management. Don’t forget to configure your DNS server after cluster creation.

Features-Ingress Controller

Unlike for cluster, NGINX Ingress Controller for platform is selected by default and cannot be disabled.

Full Kublr Platform Credentials

Applicable for:
ProviderAWS, Azure
TypePlatform

Set and confirm the password to be used to login into the deployed Kublr Platform. Please use admin as Username and these credentials as Password.