Cluster & Platform Parameters

Below you can find descriptions for basic and advanced parameters of clusters and platforms along with the recommendations on how to combine these parameters to create specific configurations.

Notes * Besides standalone, the parameters are described by meaningful groups. * For different providers (AWS, Azure and others), a group may have minor differences in meaning and description.

Basic Parameters

Basic parameters are specified in the corresponding sections:

  • General (top one)
  • Master Configuration
  • Instance Group (for each group separately)

Region

|Aplicable for:| |————-|————–| | Provider | AWS, Azure | | Type | Cluster, Platform | | Section | General |

Kublr can host cluster resources in one of multiple geographic areas referred to as regions by the provider (AWS, Azure). Please select a region to create your cluster. You can find more details * For AWS - here. * For Azure - here.

Kubernetes Version

|Aplicable for:| |————-|————–| | Provider | AWS, Azure, GCP, VMware vSphere | | Type | Cluster, Platform | | Section | General |

Defines Kubernetes version for your cluster. By default, the latest version is suggested. If you need one of the previous versions, select it from the list. This may be usefull if you are planning to deploy in Kublr cluster some applications currently not supporting the latest version of Kublr.

Note If you do not see the version you need in the list, contact Kublr support for assistance.

Instance Type and Quantity

|Aplicable for:| |————-|————–| | Provider | AWS, Azure, GCP, VMware vSphere | | Type | Cluster, Platform | | Section | Master, Instance Group |

The Instance Type parameter along with the Masters (for master nodes section) or Nodes (for work node groups) define which nodes and how many of them should act in your cluster as master and work nodes (separately for each group).

Before setting, see Kublr minimum hardware recommendations.

For AWS

Recommended configurations:

  • 1 / t2.medium for development / staging environment clusters
  • 3 / t2.medium for staging / low traffic production environments
  • 3 / m4.large for robust large production environments

See details here.

For Azure

Recommended configurations:

  • 1 / Standard_D2_v2 for development / staging environment clusters
  • 3 / Standard_A2_v2 for staging / low traffic production environments
  • 3 / Standard_D3_v2 for robust large production environments

See details here.

For GCP

Recommended configurations:

  • 1 / n1-standard-2 for development / staging environment clusters
  • 3 / n1-standard-2 for staging / low traffic production environments
  • 3 / n1-standard-2 for robust large production environments

See details here.

For VMware vSphere

For VMware vSphere, intead of the Instance Type parameter, the following parameters are used for VM (node) initialization:

  • VM Template Kublr Supports different initialization schemes provided by vSphere. If you don’t have template, please create one as specified here.
  • VM Initialization Type that can use to VM customization

Operating System

|Aplicable for:| |————-|————–| | Provider | AWS, Azure, GCP | | Type | Cluster, Platform | | Section | Master, Instance Group |

The Operating System parameter can be defined separately for master nodes and each work node group.

Public SSH Key

|Aplicable for:| |————-|————–| | Provider | AWS, Azure | | Type | Cluster, Platform | | Section | Master, Instance Group |

To login to your cluster master or work nodes via SSH, create a key pair within your provider console and select the name of the key pair in this field. You can login to your master or work nodes once the cluster is created.

The Public SSH Key is:

  • Optional:
    • For AWS. More details can be found here.
    • For GCP. More details can be found here.
  • Required for Azure.

VMware General

|Aplicable for:| |————-|————–| | Provider | VMware vSphere | | Type | Cluster | | Section | General |

As soon as you connected to VMware vSphere by setting the Credentials, you can select provided:

  • Datacenter
  • Resource Pool (belongs to selected Datacenter)
  • Datastore Type and Datastore (belongs to selected Datacenter). Kublr supports all Datastore types provided by vSphere, including Datastore Clusters.
    • Use “Regular” - for local/shared VMFS, NFS and vSAN datastores.
    • Use “Cluster” - for SRDS enabled Datastore Clusters

See also: VM Override.

Search for the related information in the VMware vSphere Documentation.

Network Configuration

|Aplicable for:| |————-|————–| | Provider | VMware vSphere | | Type | Cluster | | Section | Network Configuration |

As soon as you selected the Datacenter, you can configure the VMware network.

You can select the Network from the list and specify Network CIDR for it.

Additionally, you can:

  • In the Network Gateway type in the gateway IP address for selected Network (for example, 192.168.1.1). If omitted - it will be selected automatically, based on provided CIDR block.
  • Type in the Network Bitmask for selected Network (for example, 24). If omitted - it will be selected automatically, based on provided CIDR block.
  • Form the list of DNS Servers available in selected Network. If omitted - Google Public DNS servers (8.8.8.8 and 8.8.4.4) will be used.

Master 1: IP

|Aplicable for:| |————-|————–| | Provider | VMware vSphere | | Type | Cluster | | Section | Master, Instance Group |

IP or DNS of master node. This is required for each master to be connected with other master nodes using this IP address or DNS name. If more than 1 master node are expected then Master 2: IP, Master 3: IP and so on will also be presented and required.

CPUs

|Aplicable for:| |————-|————–| | Provider | VMware vSphere | | Type | Cluster | | Section | Master, Instance Group |

Number of CPU cores to use per VM. Make sure at least 2 CPU cores per VM. Please refer to minimum hardware recommendations.

RAM in GB

|Aplicable for:| |————-|————–| | Provider | VMware vSphere | | Type | Cluster | | Section | Master, Instance Group |

Amount of RAM to use per VM. Make sure at least 4 GB per VM. Please refer to minimum hardware recommendations.

Advanced Parameters

All advanced parameters are hidden by default and are expanded o clicking the Advanced Options control in the corresponding section.

Enable Termination Protection

|Aplicable for:| |————-|————–| | Provider | AWS | | Type | Cluster, Platform | | Section | General |

If selected, this will not be possible later to delete created cluster via the Kublr - deletion will only be possible using the AWS console user interface.

VPC

|Aplicable for:| |————-|————–| | Provider | AWS | | Type | Cluster, Platform | | Section | General |

In the VPC ID, type in the ID of existing VPC. All resources will be provisioned in this VPC. For more information, see the documentation.

In the VPC IP CIDR block, type in the CIDR block to use for the VPC.

AWS IAM

|Applicable for:| |————-|————–| | Provider | AWS | | Type | Cluster, Platform | | Section | General |

You can set separately for master and working nodes, the path associated with the existing role (type in Role Path Name) and AWS EC2 instance profile (type in Instance Profile). For more information, see the documentation.

Availability Zones

|Applicable for:| |————-|————–| | Provider | AWS | | Type | Cluster, Platform | | Section | Master |

Check Automatic to let Kublr selecting availability zones for each master node (Auto mode). In auto mode Kublr will try to spread masters over different availability zones.

Or: un-check Automatic and select availability zone for each master node from the Master 1, Master 2, … lists.

Enable Detailed Monitoring

|Applicable for:| |————-|————–| | Provider | AWS | | Type | Cluster, Platform | | Section | Master, Intance Group |

Select the option to enable CloudWatch detailed Monitoring. More details here.

Enable Spotinst Elastigroup

|Applicable for:| |————-|————–| | Provider | AWS | | Type | Cluster, Platform | | Section | Master, Intance Group |

Select the option to sue Spotinst Elastigroups instead of regular AWS Auto Scaling Groups.

VM Override

|Aplicable for:| |————-|————–| | Provider | VMware vSphere | | Type | Cluster | | Section | Master, Instance Group |

The Resource Pool and Datastore Type/Datastore defined in general VMware vSphere cluster settings, may be overridden by specific settings for any particular group of master of work nodes. This is done with the help of the following parameters:

  • Resource Pool (Override)
  • Datastore (Override)