Below you can find descriptions for the features you can optionally add to your clusters and platforms.
Notes * Besides standalone, the features are described by meaningful groups. * For different providers (AWS, Azure and others), a group may have minor differences in meaning and description.
To access the features information, in your cluster or platform dialog, scroll to the Features section at the bottom.
|Aplicable for:| |————-|————–| | Provider | AWS, Azuure, GCP, VMware vSphere | | Type | Cluster, Platform |
Refer to the detailed overview in the Logging article.
Application and systems logs can help you to understand what is happening inside your clusters. The logs are particularly useful for debugging problems and monitoring cluster activity.
The Self-hosted ElasticSearch/Kibana is useful when you need dedicated Logging in the cluster. It is recommended to use the Self-hosted ElasticSearch/Kibana for the development, staging and production environments.
Select the Add Self-hosted Elasticsearch/Kibana option for log records to be transferred both into Centralized and Self-hosted ElasticSearch.
When selected, you may additionally specify:
The Persistence enabled option is selected by default.
Optionally, you can also specify the Data node disk size in GB. Note that a 4 GB storage will be created for additionally each m..a..aster node.
Unlike cluster:
|Aplicable for:| |————-|————–| | Provider | AWS, Azure, GCP, VMware vSphere | | Type | Cluster, Platform |
Refer to the detailed overview in the Monitoring article.
Kublr provides you with detailed resource usage information on your running cluster at all levels. This will provide you with deep insights into how applications are performing and where possible bottlenecks may be found. If you want additional monitoring for your cluster, select Add Self-hosted Prometheus/Grafana/AlertManager and specify whether you want to use:
With Disk size for each. Also, enable or disable persistence for each option.
Unlike cluster:
|Aplicable for:| |————-|————–| | Provider | AWS, Azure, GCP, VMware vSphere | | Type | Cluster, Platform |
To better manage ingress http connections, load balance traffic, and terminate SSL for your services, we recommend using an Ingress controller. 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.
Unlike cluster, for a platform the NGINX Ingress Controller is selected by default and cannot be disabled.
|Aplicable for:| |————-|————–| | Provider | AWS, Azure | | Type | Platform |
Set and confirm the password to be used to login to the deployed Kublr Platform. Please use admin as Username and this credentials as Password.
