Cluster & Platform Features

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

Notes

  • Besides standalone, the features are described via (?) meaningful groups.
  • Each particular group can have minor differences in meaning and description depending on a provider (AWS, Azure and others)

Features

To access the features information, in your cluster or platform dialog, scroll to the Features section at the bottom.

Logging

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

Refer to the detailed overview in the Logging article.

For Cluster

Application and systems logs can help you understand what is happening inside your clusters. The logs are particularly useful for debugging problems and monitoring cluster activity.

The Self-hosted ElasticSearch/Kibana can be used when you need dedicated Logging in the cluster. It is recommended to apply the Self-hosted ElasticSearch/Kibana for the development, staging and production environment.

Select the Add Self-hosted Elasticsearch/Kibana option for log records to be transferred both into Centralized and Self-hosted ElasticSearch.

When selected, you can additionally specify:

  • 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

At all levels of operation Kublr provides you with detailed resource usage information on your running cluster. You receive the full vision of application performance and possible issue detection. If you need additional capacity for monitoring your cluster, select Add Self-hosted Prometheus/Grafana/AlertManager and specify whether you want to use:

  • Prometheus and/or
  • Grafana

You get particular Disk size as well as enable or disable persistence for each option.

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

We recommend using Ingress controller for: *better management of ingress http connections *better load of balance traffic *termination of SSL for your services

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.