Create Cluster

Pre-requisites to a successful cluster creation

Before creating clusters, please make sure of the following:

➤  The account has not exceeded the VPC limit
➤  The account can have KMS keys made
➤  EIP quota on the account is within limits i.e. 5 on your cloud provider account
➤  Instance limit has not been reached on your cloud provider account
➤  The roles limit has not been exceeded on your cloud provider account

Atmosly checks for the above while creating clusters.

Create a cluster

1. Navigate to the Cluster module from the left menu
2. Click on ‘Add Cluster’ in the top right corner

3. Next, fill in the required fields.
   

PLEASE NOTE: The Target account will populate based on the integrations performed.

4. Choose which type of environment you want to create, prod or non-prod.
5. Based on your selection, you will need a few additional details for a successful cluster creation.

6. Select the add-ons you want to have on your cluster, preview the configuration and the estimate cost, and CREATE!

Alternatively, you also have the option to create clusters in ONE CLICK . Navigate to this document to learn more about the functionality of one-click cluster in Atmosly.

Addons

Atmosly provides you options to choose from 5 add ons-

1. PGL STACK - Contains Prometheus for monitoring, Grafana for visualization, and Loki for log aggregation.
2. INGRESS ALB CONTROLLER - Manages AWS ALB instances for routing external traffic to services.
3. NGINX INGRESS CONTROLLER - Handles routing of external HTTP/S traffic to Kubernetes services.
4. CERT MANAGER - Automates management and issuance of TLS certificates within your cluster.
5. EFS STORAGE CLASS - Integrates AWS EFS with Kubernetes for persistent storage solutions.
   
6. K8s Dashboard - Web interface for managing, monitoring K8s clusters, simplifying cluster administration.
7. ARGOFLOW - This is to define if the cluster would run CI engine.
8. KEDA - Event-driven autoscaling for Kubernetes applications.
9. RELOADER - Auto-reloads deployments on ConfigMap or Secret changes.

Once the Cluster goes into creating status, you will see an overview section where you can find details associated with your Cluster creation.

Refer to the table below for various fields and values associated with creating clusters:

Name	Description
Display Name (mandatory)	What you want your cluster to be called. PLEASE NOTE: Name cannot contain special characters and should be unique.
Target account (mandatory)	The target account against which you want your Cluster created.
Region (mandatory)	Cloud provider region in which you want your Cluster. A region is a specific geographical location where cloud resources will be clustered.
Environment (mandatory)	Select the type of environment, prod or non-prod (Staging, QA, etc)
Availability Zones (mandatory)	Once the region is selected, you will be able to see available AZs. Each region comprises multiple Availability Zones (AZs). These AZs are separate data centers housed in separate facilities with redundant power, networking, and connectivity.
Kubernetes version (mandatory)	PLEASE NOTE: We currently support four K8 versions 1.24 - 1.27.We are working on supporting the latest K8 versions - you'll be able to see them under this field.
VPC CIDR (mandatory)	VPC (Virtual Private Cloud) CIDR (Classless Inter-Domain Routing): This refers to the IP address range for your VPC. The CIDR notation determines how the VPC's IP address space is divided and how large it is. For example, a CIDR block of 10.0.0.0/16 provides up to 65,536 private IP addresses. By default we have set the value to: 10.0.0.0/16
Tags	These are key-value pairs that you can attach to AWS resources. They are used for resource identification, organization, and management. For instance, you might tag different resources with their respective project names, environments (like prod, dev, test), or cost centers for tracking and billing purposes.
Cluster and VPC flow log (mandatory in case your Environment type = prod)	Cluster Flow Log: This typically refers to logging for resources like EKS (Elastic Kubernetes Service) clusters, capturing information about the IP traffic going to and from network interfaces in your cluster. VPC Flow Log: This is a feature that enables you to capture information about the IP traffic going to and from network interfaces in your VPC.
Cluster log retention period (mandatory if Cluster and VPC flow logs = enabled)	This term refers to the length of time that logs (such as application logs, API logs, or audit logs) for a cluster are kept. By default, we have set the value to 90 days.
VPC flow log retention period (mandatory if Cluster and VPC flow logs = enabled)	Similar to cluster log retention, this is the duration for which VPC flow logs are stored. By default, we have set the value to 60 days.
VPC flowlog max aggregation interval (mandatory if Cluster and VPC flow logs = enabled)	This refers to the maximum time interval for aggregating data in VPC flow logs. It determines how frequently log records are published to CloudWatch Logs (for AWS). By default, we have set the value to 600 seconds.
Control Plane Logging (mandatory if Cluster and VPC flow logs = enabled)	This provides audit and diagnostic logs directly from the Amazon EKS control plane to CloudWatch Logs in your account. These logs make it easy for you to secure and run your clusters.

It can take up to 20 minutes for a cluster to become ACTIVE on Atmosly